| 2.1 |
Meeting agenda and meeting reports |
|
| R4-2304000 |
RAN4#106 Meeting Report |
ETSI MCC |
| R4-2304001 |
Agenda for RAN4 #106-bis-e |
RAN4 Chair (Huawei) |
| R4-2304002 |
RAN4#106-bis-e Meeting Arrangements and Guidelines |
RAN4 Chair (Huawei) |
| 3 |
Incoming LS |
|
| R4-2304003 |
LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#112 |
RAN1 |
| R4-2304004 |
LS to RAN4 for results of the LLS performance evaluation of MPR/PAR reduction solutions |
RAN1 |
| R4-2304005 |
LS on interference modelling for duplex evolution |
RAN1 |
| R4-2304006 |
LS on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs |
RAN1 |
| R4-2304007 |
LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM |
RAN1 |
| R4-2304008 |
LS on Rel-16 UL Tx Switching period |
RAN1 |
| R4-2304009 |
LS on 1-symbol PRS |
RAN1 |
| R4-2304010 |
LS to RAN2/4 on Agreements for Rel-18 MIMO |
RAN1 |
| R4-2304011 |
Reply LS to RAN4 on PSFCH configured power with multiple resource pools |
RAN1 |
| R4-2304012 |
Response LS on enhanced cell reselection requirements in NTN |
RAN2 |
| R4-2304013 |
Reply LS on Pemax,c of S-SSB transmission |
RAN2 |
| R4-2304014 |
LS to RAN4 on autonomous denial for IDC |
RAN2 |
| R4-2304015 |
LS on Comparison of SL-RSRP and SD-RSRP measurements |
RAN2 |
| R4-2304016 |
Response LS on extending the maximum range for NS values |
RAN2 |
| R4-2304017 |
Reply LS on FS_VMR solutions review |
RAN3 |
| R4-2304018 |
LS response on UE TxD for OTA testing |
RAN5 |
| R4-2304019 |
LS response on FR2 SEM test time reduction |
RAN5 |
| R4-2304020 |
LS on FR2 RLM/BFD and beam sweeping from multiple directions |
RAN5 |
| R4-2304021 |
Response LS on testability for beam correspondence in initial access |
RAN5 |
| R4-2304022 |
LS on 3GPP work on Energy Efficiency |
SA5 |
| R4-2304023 |
NR Bandwidth for OTA TRS testing |
GSMA TSGAP |
| R4-2304029 |
LS response on measurement of phase continuity requirements for DMRS bundling |
RAN5 |
| R4-2304030 |
Response to LS from RAN1 on transmission bandwidths for NR on dedicated spectrum less than 5 MHz |
RAN |
| R4-2304031 |
Response to LS from RAN4 on spectrum less than 5 MHz |
RAN |
| R4-2304032 |
LS on frequency arrangements for APT 600MHz |
RAN |
| R4-2304033 |
Reply to LS to 3GPP on ECC request for standardisation support related to ECC Decision (22)07 on “harmonised framework on aerial UE usage in MFCN harmonised bands” |
RAN |
| R4-2306665 |
Reply LS on intraBandENDC-Support |
RAN2 |
| 4.1.1.1 |
band combinations with UL configurations including intra-band ULCA with IMD or triple beat issues |
|
| R4-2304558 |
Correction of error for flagging CA_n7B-n26A for triple beat issue |
Skyworks Solutions Inc. |
| R4-2304957 |
Discussion on addition of CA_n71-n85 |
Nokia, T-Mobile USA |
| R4-2305595 |
TP for TR 37.718-21-11: support of DC_3A_8B_n78A, DC_3A-3A_8B_n78A with UL DC_8B_n78A |
CHTTL |
| R4-2305746 |
Triple Beat MSD Test Point for DC_3A-8B_n78A |
Skyworks Solutions Inc. |
| R4-2305782 |
Issues with invalid 2UL-3CC UL configurations requests |
Skyworks Solutions Inc. |
| R4-2306483 |
TP for TR 37.718-21-11: support of DC_3A_8B_n78A, DC_3A-3A_8B_n78A with UL DC_8B_n78A |
CHTTL, Skyworks |
| 4.1.1.2 |
Others |
|
| R4-2304328 |
Initial considerations on NR-U UL CA for NS_53 and NS_54 |
Apple |
| R4-2304580 |
Changes in MSD test point and architecture discussion for CA_n71-n85 DC_12_n71 and DC_71_n12 |
Skyworks Solutions Inc. |
| R4-2304695 |
Discussion of simulation results on UE RF NR-U UL CA MPR and A-MPR for PC5 |
Charter Communications, Inc |
| R4-2304941 |
Discussion of triple beat rules for MSD analysis |
Nokia, Nokia Shanghai Bell |
| R4-2305370 |
Addition of FR1 inter-band BCS 4 and 5 |
Huawei, HiSilicon, CATT |
| R4-2305371 |
Addition of FR1 intra-band BCS 4 and 5 |
Huawei, HiSilicon, CATT |
| R4-2305597 |
Discussion on the remaining Tx requirement for intra-band contiguous NE-DC band combinations that support single switched UL only in Rel.18 |
CHTTL |
| R4-2305598 |
draft CR for missing Tx requirement for intra-band contiguous NE-DC with single switched UL only |
CHTTL, SGS Wireless |
| R4-2305694 |
TP for 37.718-11-21 to update MSD values of DC_(n)3_n78 |
Ericsson |
| R4-2305781 |
Issues with 2UL NRU-NRU inter-band combinations and invalid intra-band non-contiguous ULCA requests |
Skyworks Solutions Inc. |
| R4-2306484 |
Addition of FR1 inter-band BCS 4 and 5 |
Huawei, HiSilicon, CATT |
| R4-2306485 |
draft CR for missing Tx requirement for intra-band contiguous NE-DC with single switched UL only |
CHTTL, SGS Wireless |
| 4.1.2 |
Moderator summary and conclusions |
|
| R4-2306181 |
Topic summary for [106-bis-e][101] NR_Baskets_Part_1 |
Moderator (Skyworks) |
| R4-2306264 |
Topic summary for [106-bis-e][101] NR_Baskets_Part_1 |
Moderator (Skyworks) |
| R4-2306477 |
WF on 2 band UL configuration with 3 non-contiguous UL clusters |
Nokia, Skyworks |
| R4-2306478 |
Draft CR on adding back CA_n7B-n26 UL configuration |
Skyworks Solutions Inc. |
| R4-2306479 |
WF on CA_n71-n85 and related band 12 and 71 combinations |
T Mobile USA, Apple, Murata, Nokia, Skyworks |
| R4-2306480 |
WF on Templates and guidelines on coexistence studies for UL configurations with intra-band ULCA |
Nokia, Nokia Shanghai Bell |
| R4-2306481 |
WF on NR-U contiguous ULCA A-MPR |
Charter Communications, Inc, Apple |
| R4-2306482 |
WF on issues with non-contiguous NRU UL CCs |
Skyworks Solutions Inc., BT plc |
| 4.2 |
Moderator summary and conclusions (for basket WI AI 7.3 to AI 7.26 ) |
|
| R4-2306182 |
Topic summary for [106-bis-e][102] NR_Baskets_Part_2 |
Moderator (Nokia) |
| R4-2306183 |
Topic summary for [106-bis-e][103] NR_Baskets_Part_3 |
Moderator (Ericsson) |
| R4-2306184 |
Topic summary for [106-bis-e][104] NR_Baskets_Part_4 |
Moderator (Nokia) |
| R4-2306186 |
Topic summary for [106-bis-e][106] LTE_NR_HPUE_FWVM |
Moderator (Nokia) |
| R4-2306187 |
Topic summary for [106-bis-e][107] HPUE_Basket_EN-DC |
Moderator (Ericsson) |
| R4-2306188 |
Topic summary for [106-bis-e][108] HPUE_Basket_Intra-CA_TDD |
Moderator (Hisilicon) |
| R4-2306189 |
Topic summary for [106-bis-e][109] HPUE_Basket_inter-CA_SUL |
Moderator (China Telecom) |
| R4-2306190 |
Topic summary for [106-bis-e][110] HPUE_Basket_FDD |
Moderator (China Unicom) |
| R4-2306191 |
Topic summary for [106-bis-e][111] LTE_NR_Other_WI |
Moderator (Huawei) |
| R4-2306265 |
Topic summary for [106-bis-e][102] NR_Baskets_Part_2 |
Moderator (Nokia) |
| R4-2306266 |
Topic summary for [106-bis-e][103] NR_Baskets_Part_3 |
Moderator (Ericsson) |
| R4-2306267 |
Topic summary for [106-bis-e][104] NR_Baskets_Part_4 |
Moderator (Nokia) |
| R4-2306269 |
Topic summary for [106-bis-e][106] LTE_NR_HPUE_FWVM |
Moderator (Nokia) |
| R4-2306270 |
Topic summary for [106-bis-e][107] HPUE_Basket_EN-DC |
Moderator (Ericsson) |
| R4-2306271 |
Topic summary for [106-bis-e][108] HPUE_Basket_Intra-CA_TDD |
Moderator (Hisilicon) |
| R4-2306272 |
Topic summary for [106-bis-e][109] HPUE_Basket_inter-CA_SUL |
Moderator (China Telecom) |
| R4-2306273 |
Topic summary for [106-bis-e][110] HPUE_Basket_FDD |
Moderator (China Unicom) |
| R4-2306274 |
Topic summary for [106-bis-e][111] LTE_NR_Other_WI |
Moderator (Huawei) |
| 4.3.1 |
Rapporteur input |
|
| R4-2305574 |
TR 37.718-11-11 v0.5.0 Rel-18 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
| 4.3.2 |
UE RF requirements without FR2 band |
|
| R4-2304089 |
Draft CR for TS 38.101-3 to add DC_7A-7A_n40A |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304972 |
TP to TR 37.718-11-11 Addition of DC_1_n105 |
Nokia, Spark NZ Ltd |
| R4-2304973 |
TP to TR 37.718-11-11 Addition of DC_3_n105 |
Nokia, Spark NZ Ltd |
| R4-2304974 |
TP to TR 37.718-11-11 Addition of DC_7_n105 |
Nokia, Spark NZ Ltd |
| R4-2305575 |
TP for TR 37.718-11-11: support of uplink DC_8B_n78A |
CHTTL |
| R4-2306488 |
Draft CR for TS 38.101-3 to add DC_7A-7A_n40A |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2306496 |
TP to TR 37.718-11-11 Addition of DC_1_n105 |
Nokia, Spark NZ Ltd |
| R4-2306497 |
TP to TR 37.718-11-11 Addition of DC_3_n105 |
Nokia, Spark NZ Ltd |
| R4-2306498 |
TP to TR 37.718-11-11 Addition of DC_7_n105 |
Nokia, Spark NZ Ltd |
| 4.3.3 |
UE RF requirements with FR2 band |
|
| R4-2304740 |
Draft CR for TS 38.101-3 on support of DC_1A_n258(2G) and DC_7A_n258(2G) configurations |
ZTE Corporation |
| R4-2304959 |
Draft CR 38.101-3 to add 2CA combinations of 2 4 66 n258.docx |
Nokia |
| R4-2304967 |
Draft CR 38.101-3 to add 2CA combinations of n2 n48 n258 |
Nokia, US Cellular |
| R4-2306494 |
Draft CR 38.101-3 to add 2CA combinations of n2 n48 n258 |
Nokia, US Cellular |
| 4.4.1 |
Rapporteur input |
|
| R4-2305310 |
TR 37.718-21-11 V0.5.0 for DC of 2 LTE band and 1 NR band |
Huawei, HiSilicon |
| 4.4.2 |
UE RF requirements without FR2 band |
|
| R4-2304061 |
Draft CR for TS 38.101-3 to add DC_1A-7A-7A_n40A, DC_3A-7A-7A_n40A and DC_5A-7A-7A_n40A |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304090 |
Draft CR for TS 38.101-3 to add DC_1A-7A-7A_n40A, DC_3A-7A-7A_n40A and DC_5A-7A-7A_n40A |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304861 |
TP for 37.718-21-11 to include DC_3-67_n3 |
Ericsson, BT plc |
| R4-2304862 |
TP for 37.718-21-11 to include DC_67-(n)3 |
Ericsson, BT plc |
| R4-2304863 |
TP for 37.718-21-11 to include DC_20-67_n3 |
Ericsson, BT plc |
| R4-2304960 |
Draft CR 38.101-3 to add 3CA combinations of 2 4 7 28 38 n78.docx |
Nokia |
| R4-2305011 |
Draft CR 38.101-3 to add DC 2 bands LTE and 1 band NR |
Ericsson, Telstra |
| R4-2305145 |
TP for TR 37.718-21-11 DC_3A-8A_n41A |
ZTE Corporation |
| R4-2305311 |
TP for TR 37.718-21-11: update the tables for ?TIB and ?RIB values |
Huawei, HiSilicon |
| R4-2305576 |
TP for TR 37.718-21-11: support of DC_7A_8B_n78A, DC_7A-7A_8B_n78A with UL DC_8B_n78A |
CHTTL |
| R4-2306489 |
Draft CR for TS 38.101-3 to add DC_1A-7A-7A_n40A, DC_3A-7A-7A_n40A and DC_5A-7A-7A_n40A |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2306491 |
TP for 37.718-21-11 to include DC_3-67_n3 |
Ericsson, BT plc |
| R4-2306492 |
TP for 37.718-21-11 to include DC_67-(n)3 |
Ericsson, BT plc |
| R4-2306493 |
TP for 37.718-21-11 to include DC_20-67_n3 |
Ericsson, BT plc |
| R4-2306499 |
Draft CR 38.101-3 to add DC 2 bands LTE and 1 band NR |
Ericsson, Telstra |
| R4-2306652 |
TP for TR 37.718-21-11 DC_3A-8A_n41A |
ZTE Corporation, Skyworks |
| 4.4.3 |
UE RF requirements with FR2 band |
|
| R4-2304961 |
Draft CR 38.101-3 to add 3CA combinations of 2 7 28 n258.docx |
Nokia |
| R4-2306655 |
Draft CR 38.101-3 to add 3CA combinations of 2 7 28 n258.docx |
Nokia |
| 4.5.2 |
UE RF requirements without FR2 band |
|
| R4-2304062 |
Draft CR for TS 38.101-3 to add DC_1A-3A-5A-7A-7A_n40A and relevant fallback combinations |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304091 |
Draft CR for TS 38.101-3 to add DC_1A-3A-5A-7A-7A_n40A and relevant fallback combinations |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304741 |
Draft CR for TS 38.101-3 on support of DC_1A-1A-3A-20A_n78A and DC_1A-1A-7A-20A_n78A configurations |
ZTE Corporation |
| R4-2304963 |
Draft CR 38.101-3 to add 4CA combinations of 2 4 7 28 38 n78.docx |
Nokia |
| R4-2305012 |
Draft CR 38.101-3 to add DC x(345) bands LTE and 1 band NR |
Ericsson, Telstra |
| R4-2305367 |
Draft CR for 38.101-3 to add the missing configuration DC_3C-7A-20A-38A_n78A and DL_3C-7A-38A_n78A_UL_3C_n78A |
Huawei, HiSilicon, Deutsche Telekom |
| R4-2306490 |
Draft CR for TS 38.101-3 to add DC_1A-3A-5A-7A-7A_n40A and relevant fallback combinations |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2306500 |
Draft CR 38.101-3 to add DC x(345) bands LTE and 1 band NR |
Ericsson, Telstra |
| 4.6.1 |
Rapporteur input |
|
| R4-2304088 |
TR 37.718-11-21 v0.5.0 TR Update for DC_R18_xBLTE_2BNR_yDL2UL |
LG Electronics Deutschland |
| 4.6.2 |
UE RF requirements without FR2 band |
|
| R4-2304063 |
Draft CR for TS 38.101-3 to add DC_1A_n40A-n77(2A), DC_3A_n40A-n77(2A), DC_5A_n40A-n77(2A), DC_7A_n40A-n77(2A) and DC_5A_n40A-n78C |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304064 |
TP for TR 37.718-11-21 to include DC_1-3_n40-n77 |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304065 |
TP for TR 37.718-11-21 to include DC_1-5_n40-n77 |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304066 |
TP for TR 37.718-11-21 to include DC_1-7_n40-n77 |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304067 |
TP for TR 37.718-11-21 to include DC_3-5_n40-n77 |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304068 |
TP for TR 37.718-11-21 to include DC_3-7_n40-n77 |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304069 |
TP for TR 37.718-11-21 to include DC_5-7_n40-n77 |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304070 |
TP for TR 37.718-11-21 to include DC_1-5_n40-n78 |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304071 |
TP for TR 37.718-11-21 to include DC_3-5_n40-n78 |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304072 |
TP for TR 37.718-11-21 to include DC_5-7_n40-n78 |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2304864 |
TP for 37.718-11-21 to include DC_3_n3-n7 |
Ericsson, BT plc |
| R4-2304865 |
TP for 37.718-11-21 to include DC_3_n3-n28 |
Ericsson, BT plc |
| R4-2304866 |
TP for 37.718-11-21 to include DC_3_n3-n67 |
Ericsson, BT plc |
| R4-2304968 |
Draft CR 38.101-3 to add 3CA combinations of DC_2A_n71A-n77(2A) |
Nokia, US Cellular |
| R4-2305146 |
draft CR to TS38.101-3 DC_39_n40-n41 and DC_39_n40-n79 |
ZTE Corporation |
| R4-2305368 |
Draft CR for 38.101-3 to remove the duplicated configuration DC_3A-7A-32A_n1A-n78A |
Huawei, HiSilicon, Deutsche Telekom |
| R4-2305649 |
draft CR to TS38.101-3: DC_3A_n8A-n77A, DC_3A_n8A-n77(2A) |
Huawei Technologies France |
| R4-2305650 |
TP for TR 37.718-11-21 DC_1A_n3A-n8A |
Huawei Technologies France |
| R4-2306487 |
TP for TR 37.718-11-21 to include DC_1-7_n40-n77 |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2306495 |
Draft CR 38.101-3 to add 3CA combinations of DC_2A_n71A-n77(2A) |
Nokia, US Cellular |
| R4-2306501 |
TP for TR 37.718-11-21 DC_1A_n3A-n8A |
Huawei Technologies France |
| 4.6.3 |
UE RF requirements with FR2 band |
|
| R4-2304962 |
Draft CR 38.101-3 to add 3CA and 4CA combinations of 2 7 28 n7 n258 |
Nokia |
| 4.7.2 |
UE RF requirements without FR2 band |
|
| R4-2305632 |
draft CR to TS38.101-3: DC_1A_n3A-n8A-n77A, DC_1A_n3A-n8A-n77(2A) |
Huawei Technologies France |
| 4.7.3 |
UE RF requirements with FR2 band |
|
| R4-2305655 |
draft CR to TS38.101-3: DC_3A_n8A-n77A-n257AGHIJKLM, DC_3A_n8A-n77(2A)-n257AGHIJKLM, DC_1A_n3A-n8A-n257AGHIJKLM, DC_1A_n3A-n8A-n77A-n257AGHIJKLM, DC_1A_n3A-n8A-n77(2A)-n257AGHIJKLM, DC_3A_n8A-257AHIJKLM |
Huawei Technologies France |
| R4-2306502 |
draft CR to TS38.101-3: DC_3A_n8A-n77A-n257AGHIJKLM, DC_3A_n8A-n77(2A)-n257AGHIJKLM, DC_1A_n3A-n8A-n257AGHIJKLM, DC_1A_n3A-n8A-n77A-n257AGHIJKLM, DC_1A_n3A-n8A-n77(2A)-n257AGHIJKLM, DC_3A_n8A-257AHIJKLM |
Huawei Technologies France |
| 4.9.1 |
Rapporteur input |
|
| R4-2304857 |
TR 38.718-01-01 v0.3.0 Rel-18 NR Intra-band |
Ericsson |
| R4-2304942 |
TP to TR 38.718-01-01 Addition of UE co-existence studies for FDD with 2 Uplink in Intra-Band CA |
Nokia, Nokia Shanghai Bell |
| 4.9.2 |
UE RF requirements for FR1 |
|
| R4-2304736 |
Draft CR for TS 38.101-1 on corrections to mixed intra-band CA configurations |
ZTE Corporation |
| R4-2304860 |
draft CR 38.101-1 for adding NR Intra-band configurations |
Ericsson, T-Mobile US |
| R4-2304966 |
Draft CR 38.101-1 to add CA_n77B, CA_n77C and CA_n2(2A) BCS 4 and 5 |
Nokia, US Cellular |
| R4-2306474 |
Draft CR 38.101-1 to add CA_n77B, CA_n77C and CA_n2(2A) BCS 4 and 5 |
Nokia, US Cellular |
| 4.9.3 |
UE RF requirements for FR2 |
|
| R4-2304739 |
Draft CR for TS 38.101-2 on update to intra-band CA uplink configurations |
ZTE Corporation |
| 4.10.1 |
Rapporteur input |
|
| R4-2304943 |
TP to TR 38.718-02-01 Addition of UE co-existence studies for 2 Uplink in one Intra-Band CA |
Nokia, Nokia Shanghai Bell |
| R4-2305151 |
Revised WID to add missing band combinations |
ZTE Corporation |
| R4-2306473 |
TR38.718-02-01 v0.5.0 on Rel-18 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) |
ZTE |
| 4.10.2 |
UE RF requirements without FR2 band |
|
| R4-2304217 |
TP to TR 38.718-02-01 Addition of CA_n3A-n7A |
Huawei, Hisilicon |
| R4-2304218 |
TP to TR 38.718-02-01 Addition of CA_n3A-n75A |
Huawei, Hisilicon |
| R4-2304220 |
Draft CR for 38.101-1 to correct CA_n28-n75 |
Huawei, Hisilicon |
| R4-2304341 |
MSD requirements for CA_n71A-n85A |
Apple |
| R4-2304526 |
TP to TR 38.718-02-01 for CA_n46-n77 and DC_n46-n77 |
Huawei, HiSilicon, BT plc |
| R4-2304748 |
TP for TR 38.718-02-01 to include CA_n2A-n41A, CA_n2(2A)-n41A |
Ericsson, Rogers |
| R4-2304749 |
TP for TR 38.718-02-01 to include CA_n5A-n71A |
Ericsson, Rogers |
| R4-2304750 |
TP for TR 38.718-02-01 to include CA_n5A-n41A |
Ericsson, Rogers |
| R4-2304751 |
TP for TR 38.718-02-01 to include CA_n2A-n71A, CA_n2(2A)-n71A |
Ericsson, Rogers |
| R4-2304752 |
TP for TR 38.718-02-01 to include CA_n7A-n12A |
Ericsson, Rogers |
| R4-2304753 |
TP for TR 38.718-02-01 to include CA_n7A-n71A |
Ericsson, Rogers |
| R4-2304754 |
TP for TR 38.718-02-01 to include CA_n12A-n41A |
Ericsson, Rogers |
| R4-2304755 |
TP for TR 38.718-02-01 to include CA_n12A-n78A, CA_n12A-n78(2A) |
Ericsson, Rogers |
| R4-2304975 |
TP to TR 38.718-02-01 Addition of CA_n1-n105 |
Nokia, Spark NZ Ltd |
| R4-2304976 |
TP to TR 38.718-02-01 Addition of CA_n3-n105 |
Nokia, Spark NZ Ltd |
| R4-2304977 |
TP to TR 38.718-02-01 Addition of CA_n40-n105 |
Nokia, Spark NZ Ltd |
| R4-2304978 |
TP to TR 38.718-02-01 Addition of CA_n78-n105 |
Nokia, Spark NZ Ltd |
| R4-2304979 |
TP to TR 38.718-02-01 Addition of CA_n7-n105 |
Nokia, Spark NZ Ltd |
| R4-2304980 |
TP to TR 38.718-02-01 Addition of CA_n3-n102 and DC_n3-n102 |
Nokia, BT |
| R4-2304981 |
TP to TR 38.718-02-01 Addition of CA_n77-n102 and DC_n77-n102 |
Nokia, BT |
| R4-2305143 |
TP for TR38.718-02-01_removing the intra-band UL CA and high power limits information |
ZTE Corporation |
| R4-2305144 |
TP for TR38.718-02-01_CA_n3A-n41C with UL CA_n3A-n41C |
ZTE Corporation |
| R4-2305148 |
draft CR to TS38.101-1_CA_n40A-n41C BCS4 and 5 |
ZTE Corporation |
| R4-2306486 |
TP for TR 38.718-02-01 to include CA_n5A-n71A |
Ericsson, Rogers |
| R4-2306503 |
TP to TR 38.718-02-01 Addition of CA_n3A-n7A |
Huawei, Hisilicon |
| R4-2306504 |
TP to TR 38.718-02-01 Addition of CA_n3A-n75A |
Huawei, Hisilicon |
| R4-2306505 |
TP to TR 38.718-02-01 for CA_n46-n77 and DC_n46-n77 |
Huawei, HiSilicon, BT plc |
| R4-2306506 |
TP for TR 38.718-02-01 to include CA_n2A-n41A, CA_n2(2A)-n41A |
Ericsson, Rogers |
| R4-2306507 |
TP for TR 38.718-02-01 to include CA_n5A-n41A |
Ericsson, Rogers |
| R4-2306508 |
TP for TR 38.718-02-01 to include CA_n2A-n71A, CA_n2(2A)-n71A |
Ericsson, Rogers |
| R4-2306509 |
TP for TR 38.718-02-01 to include CA_n7A-n71A |
Ericsson, Rogers |
| R4-2306510 |
TP for TR 38.718-02-01 to include CA_n12A-n78A, CA_n12A-n78(2A) |
Ericsson, Rogers |
| R4-2306511 |
TP to TR 38.718-02-01 Addition of CA_n1-n105 |
Nokia, Spark NZ Ltd |
| R4-2306512 |
TP to TR 38.718-02-01 Addition of CA_n40-n105 |
Nokia, Spark NZ Ltd |
| R4-2306513 |
TP to TR 38.718-02-01 Addition of CA_n78-n105 |
Nokia, Spark NZ Ltd |
| R4-2306514 |
TP to TR 38.718-02-01 Addition of CA_n7-n105 |
Nokia, Spark NZ Ltd |
| R4-2306515 |
TP to TR 38.718-02-01 Addition of CA_n77-n102 and DC_n77-n102 |
Nokia, BT |
| R4-2306516 |
TP for TR38.718-02-01_CA_n3A-n41C with UL CA_n3A-n41C |
ZTE Corporation |
| R4-2306517 |
draft CR to TS38.101-1_CA_n40A-n41C BCS4 and 5 |
ZTE Corporation |
| 4.10.3 |
UE RF requirements with FR2 band |
|
| R4-2304723 |
Draft CR for 38.101-3 to add new inter-band NR-CA and NR-DC configurations with BCS4 and BCS5 (two bands) |
Samsung, Telus, Bell Mobility |
| R4-2304738 |
Draft CR for TS 38.101-2 on update to inter-band CA uplink configurations |
ZTE Corporation |
| R4-2304971 |
Draft CR 38.101-3 to add 2CA combinations of n105 n257 n258 |
Nokia, Spark NZ Ltd |
| R4-2305013 |
Draft CR 38.101-3 to add Inter-band CADC 2 bands DL with x(12) bands UL |
Ericsson, Telstra |
| R4-2306518 |
Draft CR for 38.101-3 to add new inter-band NR-CA and NR-DC configurations with BCS4 and BCS5 (two bands) |
Samsung, Telus, Bell Mobility |
| R4-2306519 |
Draft CR 38.101-3 to add 2CA combinations of n105 n257 n258 |
Nokia, Spark NZ Ltd |
| R4-2306520 |
Draft CR 38.101-3 to add Inter-band CADC 2 bands DL with x(12) bands UL |
Ericsson, Telstra |
| 4.11.1 |
Rapporteur input |
|
| R4-2304725 |
TR38.718-03-01 v0.5.0 on Rel-18 NR Inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
| 4.11.2 |
UE RF requirements without FR2 band |
|
| R4-2304219 |
Draft CR for 38.101-1 to add CA_n1A-n28A-n75A and so on |
Huawei, Hisilicon |
| R4-2304523 |
DraftCR Add intraband CA to the existing three bands DL CA combinations |
Huawei, HiSilicon, BT plc |
| R4-2304524 |
TP to TR 38.718-03-01 for CA_n1-n28-n46 and DC_n1-n28-n46 |
Huawei, HiSilicon, BT plc |
| R4-2304525 |
TP to TR 38.718-03-01 for CA_n1-n46-n78 and DC_n1-n46-n78 |
Huawei, HiSilicon, BT plc |
| R4-2304756 |
TP for 38.718-03-01 to include CA_n25A-n41A-n85A |
Ericsson, T-Mobile US |
| R4-2304757 |
TP for 38.718-03-01 to include CA_n25A-n66A-n85A |
Ericsson, T-Mobile US |
| R4-2304758 |
TP for 38.718-03-01 to include CA_n25A-n77A-n85A |
Ericsson, T-Mobile US |
| R4-2304759 |
TP for 38.718-03-01 to include CA_n41A-n77A-n85A |
Ericsson, T-Mobile US |
| R4-2304760 |
TP for 38.718-03-01 to include CA_n66A-n77A-n85A |
Ericsson, T-Mobile US |
| R4-2304867 |
TP for 38.718-03-01 to include CA_n1-n7-n67 and DC_n1-n7-n67 |
Ericsson, BT plc |
| R4-2304868 |
TP for 38.718-03-01 to include CA_n1-n67-n78 and DC_n1-n67-n78 |
Ericsson, BT plc |
| R4-2304869 |
TP for 38.718-03-01 to include CA_n7-n67-n78 and DC_n7-n67-n78 |
Ericsson, BT plc |
| R4-2304969 |
Draft CR for TS 38.101-1 Support of CA_n2-n71 CA_n5-n71 CA_n5-n77 CA_n12-n77 CA_n66-n77 CA_n71-n77 CA_n2-n77 |
Nokia, US Cellular |
| R4-2305125 |
Draft CR for 38.101-1 to add CA_n1A-n28A-n75A and others |
Huawei, Hisilicon, Deutsche Telekom AG |
| R4-2305141 |
TP for TR38.718-03-01_3DL_2UL CA_n28A-n39A-n40A |
ZTE Corporation |
| R4-2305142 |
TP for TR38.718-03-01_3DL_2UL CA_n3A-n8A-n79A |
ZTE Corporation |
| R4-2305369 |
Updated TP for TR 38.718-03-01 to introduce CA_n3B-n7A-n79A and CA_n3(2A)-n7A-n79A |
Huawei, HiSilicon, MTS |
| R4-2305596 |
TP for TR 38.718-03-01: support of CA_n3-n7-n8 2UL/3DL |
CHTTL |
| R4-2306521 |
TP to TR 38.718-03-01 for CA_n1-n46-n78 and DC_n1-n46-n78 |
Huawei, HiSilicon, BT plc |
| R4-2306522 |
TP for 38.718-03-01 to include CA_n25A-n66A-n85A |
Ericsson, T-Mobile US |
| R4-2306523 |
TP for 38.718-03-01 to include CA_n41A-n77A-n85A |
Ericsson, T-Mobile US |
| R4-2306524 |
TP for 38.718-03-01 to include CA_n66A-n77A-n85A |
Ericsson, T-Mobile US |
| R4-2306525 |
TP for 38.718-03-01 to include CA_n1-n7-n67 and DC_n1-n7-n67 |
Ericsson, BT plc |
| R4-2306526 |
TP for 38.718-03-01 to include CA_n1-n67-n78 and DC_n1-n67-n78 |
Ericsson, BT plc |
| R4-2306527 |
Draft CR for 38.101-1 to add CA_n1A-n28A-n75A and others |
Huawei, Hisilicon, Deutsche Telekom AG |
| R4-2306528 |
TP for TR38.718-03-01_3DL_2UL CA_n3A-n8A-n79A |
ZTE Corporation |
| R4-2306529 |
TP for TR 38.718-03-01: support of CA_n3-n7-n8 2UL/3DL |
CHTTL |
| 4.11.3 |
UE RF requirements with FR2 band |
|
| R4-2304724 |
Draft CR for 38.101-3 to add new inter-band NR-CA and NR-DC configurations with BCS4 and BCS5 (three bands) |
Samsung, Telus, Bell Mobility |
| R4-2305147 |
draft CR to TS38.101-3 CA_n39A-n40A-n258A and CA_n39A-n41A-n258A |
ZTE Corporation |
| R4-2305149 |
draft CR to TS38.101-1_CA_n28A-n40A-n41C |
ZTE Corporation |
| R4-2305606 |
Draft CR for 38.101-3 NR FR1+FR2 inter-band CA combinations for 3 bands DL with 1 and 2 bands UL |
Huawei, HiSilicon |
| R4-2306530 |
Draft CR for 38.101-3 to add new inter-band NR-CA and NR-DC configurations with BCS4 and BCS5 (three bands) |
Samsung, Telus, Bell Mobility |
| R4-2306531 |
Draft CR for 38.101-3 NR FR1+FR2 inter-band CA combinations for 3 bands DL with 1 and 2 bands UL |
Huawei, HiSilicon |
| 4.12.1 |
Rapporteur input |
|
| R4-2304746 |
big CR 38.101-1 NR Inter-band CA/DC for y bands DL (y=4, 5, 6) with x bands UL (x=1, 2) |
Ericsson |
| R4-2304747 |
big CR 38.101-3 NR Inter-band CA/DC for y bands DL (y=4, 5, 6) with x bands UL (x=1, 2) |
Ericsson |
| 4.13.1 |
Rapporteur input |
|
| R4-2305366 |
Draft TR 37.718-00-00 v0.3.0 |
Huawei, HiSilicon |
| 4.13.2 |
UE RF requirements |
|
| R4-2304737 |
Draft CR for TS 38.101-1 on corrections to SUL configurations |
ZTE Corporation |
| R4-2305444 |
Discussion on the note for delta_Tib and delta_Rib in TR37.718-00-00 |
Huawei, HiSilicon |
| R4-2305445 |
TP for TR 37.718-00-00: correction on the Note for delta_Tib and delta_Rib |
Huawei, HiSilicon |
| R4-2305446 |
TP on TR37.718-00-00: SUL_n78C-n89A |
Huawei, HiSilicon |
| R4-2305586 |
TP for TR 37.718-00-00: Correction on SUL_n1A-n81A |
Huawei, HiSilicon |
| R4-2305587 |
TP on TR37.718-00-00: Correction on SUL_n1A-n81A |
Huawei, HiSilicon |
| R4-2305588 |
TP on TR37.718-00-00: Correction on SUL_n3A-n84A |
Huawei, HiSilicon |
| R4-2305589 |
TP on TR37.718-00-00: Correction on SUL_n1A-n89A |
Huawei, HiSilicon |
| R4-2305590 |
TP on TR37.718-00-00: Correction on SUL_n78A-n89A |
Huawei, HiSilicon |
| R4-2305591 |
TP for TR 37.718-00-00 Correction on CA_n78A_SUL_n1A-n81A |
Huawei, HiSilicon |
| R4-2305592 |
TP for TR 37.718-00-00 Correction on CA_n78A_SUL_n1A-n80A |
Huawei, HiSilicon |
| R4-2305593 |
TP for TR 37.718-00-00 Correction on CA_n78A_SUL_n1A-n89A |
Huawei, HiSilicon |
| R4-2305594 |
TP for TR 37.718-00-00 Correction on CA_n78A_SUL_n3A-n84A |
Huawei, HiSilicon |
| R4-2306475 |
TP for TR 37.718-00-00: Correction on SUL_n1A-n81A |
Huawei, Hisilicon |
| R4-2306653 |
TP for TR 37.718-00-00: correction on the Note for delta_Tib and delta_Rib |
Huawei, HiSilicon |
| 4.14.1 |
Rapporteur input |
|
| R4-2304652 |
Draft TR 38.718-00-02: NR Carrier Aggregation band combinations with two SUL cells |
CMCC |
| 4.14.2 |
UE RF requirements |
|
| R4-2304348 |
Notation for SUL CA combinations |
Apple |
| R4-2306546 |
WF on the notation for single SUL CA combinations |
Apple |
| 4.16.1 |
Rapporteur input |
|
| R4-2304038 |
TR 37.829 v0.5.0 |
Nokia |
| 4.16.2 |
UE RF requirements |
|
| R4-2304037 |
draftCR 38.101-1 FWA addition of bands n77 |
Nokia |
| R4-2304112 |
TP to TR 37.829: System level simulation methodology and assumptions for coexistence study on 31dBm UE Power Class for LTE Band 41 and NR Band n41 |
Nokia, T-Mobile USA |
| R4-2304113 |
TP to TR 37.829: System level simulation methodology and assumptions for coexistence study on 31dBm UE Power Class for NR Band n77 |
Nokia, T-Mobile USA |
| R4-2304114 |
System level simulation results for coexistence study on 31dBm UE Power Class for LTE Band 41 and NR Band n41 |
Nokia, T-Mobile USA |
| R4-2304115 |
TP to TR 37.829: PC1 A-MPR for LTE band 12 |
Nokia, U.S. Cellular |
| R4-2304116 |
Draft CR on addition of PC1 operation for band 12 |
Nokia, U.S. Cellular |
| R4-2305678 |
FWA PC1 n41 NS_04 A-MPR simulation results |
Nokia, Nokia Shanghai Bell |
| R4-2306533 |
Draft CR on addition of PC1 operation for band 12 |
Nokia, U.S. Cellular |
| 4.17.1 |
Rapporteur input |
|
| R4-2304858 |
TR 38.898 v0.3.0 Rel-18 High power UE for FR1 for DC_R18_xBLTE_yBNR_zDLnUL |
Ericsson |
| 4.17.2 |
UE RF requirements |
|
| R4-2305016 |
TP for TR 38.898: DC_1A_n41A |
Samsung, KDDI, Qualcomm |
| R4-2305017 |
TP for TR 38.898 DC_41A_n77A |
Samsung, KDDI, Qualcomm |
| R4-2305617 |
TP for PC2 DC_1-3_n78 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305618 |
TP for PC2 DC_1-42_n78 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305619 |
TP for PC2 DC_3-42_n78 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305620 |
TP for PC2 DC_21-42_n78 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305621 |
TP for PC2 DC_1-3_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305622 |
TP for PC2 DC_1-19_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305623 |
TP for PC2 DC_1-21_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305624 |
TP for PC2 DC_1-42_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305625 |
TP for PC2 DC_3-19_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305626 |
TP for PC2 DC_3-21_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305627 |
TP for PC2 DC_3-42_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305628 |
TP for PC2 DC_19-21_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305629 |
TP for PC2 DC_19-42_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305630 |
TP for PC2 DC_21-42_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2305631 |
Draft CR 38.101-3 to add PC2 DC_LTE(s)_n77(2A) and DC_LTE(s)_n78(2A) |
NTT DOCOMO, INC. |
| R4-2305753 |
Add the approved combinations in Rel-18 EN-DC HPUE |
Verizon, Ericsson |
| R4-2305767 |
Add single uplink to in DL combination for Rel-18 EN-DC HPUE |
Verizon Denmark |
| R4-2306534 |
TP for TR 38.898: DC_1A_n41A |
Samsung, KDDI, Qualcomm |
| R4-2306535 |
TP for TR 38.898 DC_41A_n77A |
Samsung, KDDI, Qualcomm |
| R4-2306536 |
TP for PC2 DC_1-21_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2306537 |
TP for PC2 DC_3-42_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2306538 |
TP for PC2 DC_19-42_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2306539 |
TP for PC2 DC_21-42_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| 4.18.1 |
Rapporteur input |
|
| R4-2305493 |
TP on TR 38.897 for DL CA_n41(A-C) with UL PC2 CA_n41c |
Huawei,HiSilicon |
| R4-2305494 |
TP on TR 38.897 for DL CA_n77(3A) with UL PC2 and PC1.5 n77 |
Huawei,HiSilicon |
| R4-2305499 |
WID on HPUE_NR_FR1_TDD_intra_CA_R18 |
Huawei,HiSilicon |
| R4-2305500 |
TR 38.897-020 |
Huawei,HiSilicon |
| R4-2305692 |
Missing general and specific requirements for PC1.5 intra-band ULCA UL configuration request for inter-band HPUE |
Skyworks Solutions Inc. |
| R4-2306540 |
Draft CR on TS38.101-1 Addition of intra-band CA Combinations |
Huawei, HiSilicon |
| 4.18.2 |
UE RF requirements with PC2 and PC1.5 |
|
| R4-2305495 |
Draft CR on TS38.101-1 Addition of CA_n77C with UL PC1.5 n77 |
Huawei,HiSilicon |
| R4-2305496 |
Draft CR on TS38.101-1 Addition of CA_n77C with UL PC2 CA_n77C |
Huawei,HiSilicon |
| 4.19.1 |
Rapporteur input |
|
| R4-2304281 |
TR 38.895 v0.2.0 TDD PC1_5 HPUE |
CMCC |
| 4.19.2 |
UE RF requirements |
|
| R4-2304582 |
Handling of new 35MHz CBW for n39 and n98 |
Skyworks Solutions Inc. |
| R4-2305505 |
NS_50 measurements and A-MPR |
Qualcomm Inc. |
| 4.20 |
High power UE for FR1 NR inter-band CA/DC or SUL band combination with y DL-x UL and PCm (m<3) and high power on TDD |
|
| R4-2305743 |
On SUL PC2 Requirements |
Skyworks Solutions Inc. |
| R4-2306541 |
WF on PC1.5 NS_47 and SUL PC2 specification impacts. |
Skyworks Solutions Inc. |
| 4.20.1 |
Rapporteur input |
|
| R4-2304522 |
TR for High power UE for FR1 NR inter-band CA/DC or NR SUL band combination with y (1
| Huawei, HiSilicon, China Telecom |
|
| R4-2304665 |
Discussion on handling PC2+PC2 UL inter-band CA combinations |
China Telecom |
| 4.20.2 |
UE RF requirements with PC2 and PC1.5 |
|
| R4-2304579 |
NS_47 work needed for n41 PC1.5 1UL configuration in HPUE CA_n3-n41 |
Skyworks Solutions Inc. |
| R4-2304958 |
Draft CR 38.101-1 to add HPUE for 2 3 4 CA of n25 n41 n66 n71 n77 |
Nokia, T-Mobile USA |
| R4-2304970 |
Draft CR 38.101-1 to add HPUE for 3 CA of n2 n5 n48 n66 n77 |
Nokia, Verizon |
| R4-2305018 |
TP for HPUE CA_n3-n28-n77 with 1UL and 2UL for TR 38.899 |
Samsung, KDDI, Qualcomm |
| R4-2305019 |
TP for HPUE CA_n28-n41-n77 with 1UL and 2UL for TR 38.899 |
Samsung, KDDI, Qualcomm |
| R4-2305020 |
TP for HPUE CA_n28-n77 with 1UL and 2UL for TR 38.899 |
Samsung, KDDI, Qualcomm |
| R4-2305038 |
Draft CR for TS 38.101-1: Addition of inter-band PC2 CA Combinations |
KDDI Corporation, Samsung |
| R4-2305150 |
draft CR to TS 38.101-1 Add maximum output power for HPUE CA_n3-n77 configuration |
ZTE Corporation |
| R4-2305829 |
PC1.5 inter-band UL CA |
T-Mobile USA |
| R4-2305830 |
Draft CR for 38.101-1: PC1.5 UL CA_n41A-n77A |
T-Mobile USA |
| R4-2306542 |
Draft CR 38.101-1 to add HPUE for 2 3 4 CA of n25 n41 n66 n71 n77 |
Nokia, T-Mobile USA |
| R4-2306543 |
Draft CR 38.101-1 to add HPUE for 3 CA of n2 n5 n48 n66 n77 |
Nokia, Verizon |
| 4.21.1 |
Rapporteur input |
|
| R4-2304471 |
TR 38.850 v0.2.0 HPUE_FR1_FDD_NR_CADC_R18 |
China Unicom |
| R4-2306544 |
FDD HPUE Basket WIs |
China Unicom |
| 4.21.2 |
UE RF requirements |
|
| R4-2304470 |
TP for TR38.850 Correction of Note 8 under CA configuration table |
China Unicom |
| 4.22.2 |
UE RF requirements |
|
| R4-2304084 |
Discussion on 2TX PC2 FDD bands Reference Sensitivity Degradation |
Spreadtrum Communications |
| R4-2304472 |
Discussion on reference sensitivity degradation requirements for FDD PC2 HPUE |
China Unicom |
| R4-2304509 |
Discussion on PC2 FDD bands Reference Sensitivity Degradation |
Mediatek India Technology Pvt. |
| R4-2304517 |
MSD for PC2 FDD bands |
Huawei, HiSilicon |
| R4-2304518 |
PC2 A-MPR for band n8 NS_43 |
Huawei, HiSilicon |
| R4-2304519 |
PC2 A-MPR for band n28 NS_18 |
Huawei, HiSilicon |
| R4-2304581 |
Handling of new n8 and n71 CBW for PC2 FDD bands RSD and A-MPR |
Skyworks Solutions Inc. |
| R4-2305364 |
Corrections on MSD for PC2 FDD bands with 2Tx |
Apple |
| R4-2305393 |
PC2 FDD bands RSD |
Murata Manufacturing Co Ltd. |
| 4.23.1 |
Rapporteur input |
|
| R4-2305155 |
TR 37.877 0.3.0 draft TR for Rel-18 downlink interruption for NR and EN-DC band combinations at dynamic Tx switching |
China Telecom |
| 4.23.2 |
UE RF requirements |
|
| R4-2305153 |
Discussion on release independence on mandating no DL interruption for Tx Switching |
China Telecom |
| R4-2305154 |
TP to TR 37.877 Release independence on mandating no DL interruption for Tx Switching |
China Telecom |
| R4-2306549 |
TP to TR 37.877 Release independence on mandating no DL interruption for Tx Switching |
China Telecom |
| 4.24.1 |
Rapporteur Input |
|
| R4-2305605 |
Big CR for 38.101-1 introduce UL MIMO configurations for Rel-18 |
Huawei, HiSilicon |
| 4.25.1 |
Rapporteur input |
|
| R4-2305643 |
Redcap operating band RF impact analysis |
Ericsson |
| 4.25.2 |
UE RF requirements |
|
| R4-2305390 |
Discussion on HD-FDD REFSENS for RedCap UE |
Huawei, HiSilicon |
| R4-2305644 |
CR for adding REFSENS for HD-FDD RedCap UE for band n105 |
Ericsson |
| R4-2306548 |
CR for adding REFSENS for HD-FDD RedCap UE for band n105 |
Ericsson |
| 4.26.1 |
Rapporteur input |
|
| R4-2304576 |
Information on the last revision of the basket WID on adding channel bandwidth support to existing NR bands |
Ericsson |
| 4.26.2.1 |
Single band requirements |
|
| R4-2304349 |
On RF requirements for 25MHz and 30MHz UL CBW for n71 |
Apple |
| R4-2304556 |
Additional input for 20-25MHz UL-DL CBW for n8 |
Skyworks Solutions Inc. |
| R4-2304557 |
Additional work needed for 35MHz CBW for n39 and n98 |
Skyworks Solutions Inc. |
| R4-2304559 |
Impact of 25 and 30MHz ULDL CBW for n71 |
Skyworks Solutions Inc. |
| R4-2305820 |
25 MHz and 30 MHz uplink in Band n71 for PC3 |
Qualcomm Incorporated |
| R4-2306545 |
WF on adding new channel bandwidths support to existing NR bands |
Ericsson |
| 4.27.1 |
Rapporteur input |
|
| R4-2305442 |
Big CR for TS 38.101-1 Rel-18 Simultaneous Rx/Tx inter-band combinations |
Huawei, HiSilicon |
| R4-2305443 |
TR 38.894 v0.2.0 |
Huawei, HiSilicon |
| 4.27.2 |
Identification of simultaneous Rx/Tx capability for band combinations and UE RF requirements |
|
| R4-2304213 |
Draft CR for updating simultaneous Rx/Tx requirements for CA_n40-n41 |
CMCC |
| R4-2304319 |
On simultaneous Rx-Tx for NR inter-band combinations |
Apple |
| R4-2304871 |
Discussion simultaneous Rx/Tx inter-band combinations for CA_n40-n41 |
MediaTek Inc. |
| R4-2305140 |
TP for TR38.894_Harmonic mixing MSD for non-simultaneous RxTx CA_n39-n41 |
ZTE Corporation |
| R4-2305436 |
Cross band isolation MSD analysis for CA_n40-n41 |
Huawei, HiSilicon |
| R4-2305437 |
Cross band isolation MSD analysis for CA_n34-n41 |
Huawei, HiSilicon |
| R4-2305438 |
TP for 38.894 :CA_n7A-n40A |
Huawei, HiSilicon |
| R4-2305439 |
TP for 38.894 :CA_n39A-n41A |
Huawei, HiSilicon |
| R4-2305440 |
TP for 38.894 :CA_n34A-n41A |
Huawei, HiSilicon |
| R4-2305441 |
TP for 38.894 :CA_n40A-n41A |
Huawei, HiSilicon |
| R4-2305740 |
SRS antenna switching in TDD-TDD with simultaneous RxTx |
Skyworks Solutions Inc. |
| R4-2305741 |
SUL_n41_n97 and CA_n40-n41 simultaneous RxTx MSD |
Skyworks Solutions Inc. |
| R4-2305742 |
SUL_n41_n95 and CA_n34-n41 simultaneous RxTx MSD |
Skyworks Solutions Inc. |
| R4-2306547 |
WF on simultaneous Rx-Tx inter-band combinations |
Huawei, HiSilicon |
| R4-2306550 |
TP for TR38.894_Harmonic mixing MSD for non-simultaneous RxTx CA_n39-n41 |
ZTE Corporation |
| R4-2306551 |
TP for 38.894 :CA_n34A-n41A |
Huawei, HiSilicon |
| R4-2306552 |
TP for 38.894 :CA_n40A-n41A |
Huawei, HiSilicon |
| 4.29.2 |
Enhancements for 4Rx at low frequency band (<1GHz) |
|
| R4-2304350 |
Views on low band 4Rx for handheld UE |
Apple |
| R4-2304721 |
Views on low band 4Rx for handheld UE |
Samsung, Telus, Bell Mobility |
| R4-2305084 |
Further discussion on enhancements for 4Rx at low frequency band |
vivo |
| R4-2305135 |
Further discussion on 4Rx low band (<1GHz) for handheld UE |
ZTE Corporation |
| R4-2305290 |
Discussion on enhancement for 4Rx at low frequency band |
Google Inc. |
| R4-2305293 |
Discussion on Enhancements for 4Rx at low frequency band |
Xiaomi |
| R4-2305429 |
R18 low band 4Rx |
OPPO |
| R4-2305566 |
On 4Rx requirements for low operating bands |
Huawei, HiSilicon |
| R4-2305744 |
Views on 4Rx handheld UE for low NR bands |
Sony |
| R4-2305842 |
Discussion on UE RF requirements for 4Rx at low frequency band (<1GHz) |
Ericsson Limited |
| 4.29.3 |
Enhancements of 3Tx for band combinations with two bands |
|
| R4-2304720 |
Views on 3Tx for band combinations with 2 band |
Samsung, Telus, Bell Mobility |
| 4.29.3.1 |
Tx requirements for band combinations with 3Tx |
|
| R4-2304351 |
On simultaneous 3Tx for inter-band UL CA/DC |
Apple |
| R4-2304612 |
UE Tx requirement for inter-band CA PC1.5 and EN-DC PC1.5 with 3Tx |
LG Electronics |
| R4-2305085 |
Tx Requirements of 3Tx for band combinations with two bands |
vivo |
| R4-2305133 |
Tx requirements for 3Tx for band combinations within two bands |
ZTE Corporation |
| R4-2305291 |
discussion on Tx requirement for 3Tx for inter-band UL CA and EN-DC |
Xiaomi |
| R4-2305430 |
R18 Tx requirement for 3Tx inter-band combinations |
OPPO |
| 4.29.3.2 |
Rx requirements for band combinations with 3Tx |
|
| R4-2304352 |
Rx requirements for inter-band UL CA/DC with 3Tx |
Apple |
| R4-2305086 |
Rx Requirements of 3Tx for band combinations with two bands |
vivo |
| R4-2305134 |
Rx requirements for 3Tx for band combinations within two bands |
ZTE Corporation |
| R4-2305292 |
discussion on Rx requirement for 3Tx for inter-band UL CA and EN-DC |
Xiaomi |
| R4-2305431 |
R18 Rx requirement for 3Tx inter-band combinations |
OPPO |
| R4-2305565 |
On UE RF requirements for FWA UE supporting 3T for two bands |
Huawei, HiSilicon |
| 4.29.4 |
Moderator summary and conclusions |
|
| R4-2306192 |
Topic summary for [106-bis-e][112] NR_3Tx-4Rx_WI |
Moderator (OPPO) |
| R4-2306275 |
Topic summary for [106-bis-e][112] NR_3Tx-4Rx_WI |
Moderator (OPPO) |
| R4-2306553 |
WF on low band 4Rx |
Vivo |
| R4-2306554 |
WF on Tx requirements for 3Tx UE |
OPPO |
| R4-2306555 |
WF on Rx requirements for 3Tx UE |
Apple |
| 4.30.1 |
General and work plan |
|
| R4-2304436 |
Discussion on the work plan for WI NR_700800900_combo_enh |
CATT, China Telecom |
| R4-2305376 |
General discussion on how to implement CR for each band combination |
Huawei, HiSilicon |
| R4-2306466 |
Discussion on the work plan for WI NR_700800900_combo_enh |
CATT, China Telecom |
| 4.30.2 |
UE RF requirements and related transmission schemes |
|
| R4-2304166 |
[Draft] LS on non-simultaneous UL and DL from different two bands during UL CA |
Nokia, Nokia Shanghai Bell |
| R4-2306465 |
LS on non-simultaneous UL and DL from different two bands during UL CA |
Nokia, Nokia Shanghai Bell |
| 4.30.2.1 |
CA configuration of CA_n5-n8 |
|
| R4-2304168 |
CA_n5-n8 handling |
Nokia, Nokia Shanghai Bell |
| R4-2304353 |
CA_n5-n8 UE architecture and RF requirements |
Apple |
| R4-2304435 |
Discussion on the solutions for CA_n5-n8 |
CATT |
| R4-2304454 |
Considerations on CA_n5-n8 |
Qualcomm Finland RFFE Oy |
| R4-2304563 |
Input to CA_n5-n8 for LBLB and LBLBLB band combinations WI |
Skyworks Solutions Inc. |
| R4-2305073 |
Discussion on UE RF requirements and related transmission schemes for CA_n5-n8 |
vivo |
| R4-2305131 |
Discussion and draft LS on CA band combination of n5-n8 |
ZTE Corporation |
| R4-2305152 |
Discussion on options for overlap in CA_n5-n8 |
China Telecom |
| R4-2305253 |
Discussion on CA_n5-n8 |
Xiaomi |
| R4-2305377 |
Discussion on RF impacts and requirements for CA_n5-n28 |
Huawei, HiSilicon |
| 4.30.2.2 |
CA configuration of CA_n5-n28 |
|
| R4-2304453 |
Considerations on CA_n5-n28 |
Qualcomm Finland RFFE Oy |
| R4-2304564 |
Input to CA_n5-n28 for LBLB and LBLBLB band combinations WI |
Skyworks Solutions Inc. |
| R4-2305132 |
Views on RF requirements for CA band combination of n5-n28 |
ZTE Corporation |
| R4-2305254 |
Discussion on CA_n5-n28 |
Xiaomi |
| R4-2305379 |
Discussion on candidate solutions and RF requirements for CA_n5-n8 |
Huawei, HiSilicon |
| 4.30.2.3 |
CA configuration of CA_n8-n20-n28 |
|
| R4-2304565 |
Input to CA_n8-n20-n28 for LBLB and LBLBLB band combinations WI |
Skyworks Solutions Inc. |
| R4-2305255 |
Discussion on CA_n8-n20-n28 |
Xiaomi |
| R4-2305378 |
Discussion on RF impacts and requirements for CA_n8-n20-n28 |
Huawei, HiSilicon |
| 4.30.3 |
Moderator summary and conclusions |
|
| R4-2306193 |
Topic summary for [106-bis-e][113] NR_700800900_combo_enh |
Moderator (CATT) |
| R4-2306276 |
Topic summary for [106-bis-e][113] NR_700800900_combo_enh |
Moderator (CATT) |
| R4-2306467 |
WF on CA_n5-n8 |
Skyworks |
| R4-2306468 |
WF on CA_n5-n28 and CA_n8-n20-n28 |
Huawei, HiSilicon |
| 4.31.1 |
General and work plan |
|
| R4-2304320 |
Update of the regulatory requirements and summary of NS values |
Apple |
| R4-2304321 |
Introduction of new countries with associated NS values and A-MPR back-off |
Apple |
| R4-2304323 |
draft CR: Rolling CR covering the agreed changes for NR-U |
Apple |
| R4-2304324 |
draft CR: Adding missing requirements for NR-U Rel-16 |
Apple |
| R4-2304325 |
draft CR: Adding missing requirements for NR-U Rel-17 |
Apple |
| R4-2304940 |
Discussion on NS extension for NR-U |
Nokia, Nokia Shanghai Bell |
| R4-2306558 |
draft CR: Rolling CR covering the agreed changes for NR-U |
Apple |
| 4.31.2 |
Common requirements (channel raster, A-MPR for 100MHz CBW) |
|
| R4-2304326 |
Further considerations on extending the maximum range for NS values |
Apple |
| R4-2305648 |
[draft] Response LS on extending the maximum range for NS values |
Apple |
| R4-2305752 |
Preliminary verification of NR-U 1Tx PC3 MPR |
Skyworks Solutions Inc. |
| R4-2306560 |
Response LS on extending the maximum range for NS values |
Apple |
| 4.31.3 |
UE RF requirements for SP and LPI |
|
| R4-2304322 |
On open NR-U topics |
Apple |
| R4-2304610 |
NR-U PC3 UE RF requirements |
LG Electronics |
| R4-2304611 |
draft CR on NR-U PC3 UL-MIMO |
LG Electronics |
| R4-2306559 |
draft CR on NR-U PC3 UL-MIMO |
LG Electronics |
| 4.31.6 |
Moderator summary and conclusions |
|
| R4-2306194 |
Topic summary for [106-bis-e][114] NR_unlic_enh |
Moderator (Apple) |
| R4-2306277 |
Topic summary for [106-bis-e][114] NR_unlic_enh |
Moderator (Apple) |
| R4-2306557 |
WF on NR-U enhancement topics |
Apple |
| 4.32.1 |
General and work plan |
|
| R4-2304329 |
Draft TR for the NTN L-/S-band |
Apple, Globalstar |
| R4-2304332 |
Draft running CR on Introduction of the NTN L-/S-band to TS 38.101-5 |
Apple, Globalstar |
| R4-2304333 |
Draft running CR on Introduction of the NTN L-/S-band to TS 38.133 |
Apple, Globalstar |
| R4-2306562 |
Draft TR for the NTN L-/S-band |
Apple, Globalstar |
| R4-2306563 |
Draft running CR on Introduction of the NTN L-/S-band to TS 38.101-5 |
Apple, Globalstar |
| R4-2306564 |
Draft running CR on Introduction of the NTN L-/S-band to TS 38.133 |
Apple, Globalstar |
| 4.32.2 |
Band definition and system parameters |
|
| R4-2304330 |
System parameters for the NTN L-/S-band |
Apple, Globalstar |
| R4-2304939 |
Discussion on new FR1 NTN band (n254) |
Nokia, Nokia Shanghai Bell |
| 4.32.3 |
UE RF requirements |
|
| R4-2304331 |
RF requirements for the NTN L-/S-band |
Apple, Globalstar |
| R4-2304794 |
Discussion on UE RF requirements for the satellite L-/S-band |
ZTE Corporation |
| R4-2304795 |
CR to TS38.101-5 Introduction of the satellite L-/S-band |
ZTE Corporation |
| R4-2305297 |
Discussion on UE RF for NTN L-S- bands |
Xiaomi |
| R4-2305392 |
Discussion on UE RF requiremetns for NTN LS bands |
Huawei, HiSilicon |
| R4-2305826 |
L-/S- NTN band ETSI requirements for the UE |
Qualcomm Incorporated |
| R4-2305827 |
Compatibility between EN 301 441 and 3GPP requirements for MES |
Qualcomm Incorporated |
| 4.32.4 |
SAN RF requirements |
|
| R4-2304796 |
CR to TS38.108 Introduction of the satellite L-band and S-band |
ZTE Corporation |
| R4-2306565 |
CR to TS38.108 Introduction of the satellite L-band and S-band |
ZTE Corporation |
| 4.32.5 |
RRM requirements |
|
| R4-2305037 |
Draft CR to TS38.133: Introduction of a new NTN FDD band n254 |
ZTE Corporation |
| 4.32.6 |
Moderator summary and conclusions |
|
| R4-2306195 |
Topic summary for [106-bis-e][115] LTE_NR_NTN_LSband |
Moderator (Apple) |
| R4-2306278 |
Topic summary for [106-bis-e][115] LTE_NR_NTN_LSband |
Moderator (Apple) |
| R4-2306561 |
WF on NTN L-/S-band |
Apple |
| 5.1.1 |
General and work plan |
|
| R4-2304726 |
TR 38.846 v0.4.0_Study on simplification of band combination specification for NR and LTE |
ZTE Corporation |
| 5.1.2 |
Simplification of working procedure |
|
| R4-2304733 |
Discussion on the template for HPUE band combinations |
ZTE Corporation |
| R4-2304734 |
TP for TR 38.846 on template for R18 HPUE band combination |
ZTE Corporation |
| R4-2304735 |
Template for R18 HPUE band combinations |
ZTE Corporation |
| R4-2304859 |
TP to TR 38.846 with guidance on how to make new entries into configuration tables |
Ericsson, Nokia |
| R4-2304944 |
TP to TR 38.846 to add guidance on Co-existence studies for Uplink Intra-Band Non-Contiguous CA |
Nokia, Nokia Shanghai Bell |
| R4-2306586 |
TP for TR 38.846 on template for R18 HPUE band combination |
ZTE Corporation |
| R4-2306587 |
Template for R18 HPUE band combinations |
ZTE Corporation |
| 5.1.3 |
Simplification of specification and reduction of test burden |
|
| R4-2304039 |
Discussions on NR interband 2UL CA co-ex simplification |
Nokia |
| R4-2304040 |
draftCR 38.101-1 NR interband 2UL CA co-ex simplication R16 |
Nokia |
| R4-2305380 |
Discussion on simplification of MSD test configurations for ENDC. |
Huawei, HiSilicon |
| R4-2305381 |
TP for TR 38.846 to align the MSD test configurations due to harmonic and harmonic mixing for ENDC |
Huawei, HiSilicon |
| R4-2305748 |
PC3 cross-band isolation MSD for EN-DC simplification |
Skyworks Solutions Inc. |
| R4-2305749 |
TP for TR 38.846 on test burden reduction for multiple MSD in band combinations |
Skyworks Solutions Inc. |
| R4-2306588 |
TP for TR 38.846 on test burden reduction for multiple MSD in band combinations |
Skyworks Solutions Inc. |
| 5.1.4 |
Others |
|
| R4-2304317 |
Improvements on fallbacks for band combinations |
Apple |
| R4-2304731 |
Discussion on guidelines on valid CBW for higher order BC configurations |
ZTE Corporation |
| R4-2304732 |
TP for TR 38.846 on valid CBW for higher order BC configurations |
ZTE Corporation |
| R4-2306585 |
TP for TR 38.846 on valid CBW for higher order BC configurations |
ZTE Corporation |
| 5.2.1 |
General and work plan |
|
| R4-2304117 |
TP to TR 38.877: Summary and conclusions |
Nokia, Nokia Shanghai Bell |
| R4-2305298 |
TR 38.877 v0.3.0 |
Huawei, HiSilicon |
| R4-2305299 |
TP for Clause 3: abbreviations |
Huawei, HiSilicon |
| R4-2305300 |
Consideration on the co-location requirements |
Huawei, HiSilicon |
| R4-2305882 |
TR 38.877 v0.3.0 |
Huawei, HiSilicon |
| R4-2305883 |
TP for Clause 3: abbreviations |
Huawei, HiSilicon |
| 5.2.2 |
Investigation of mmWave multi-band BS |
|
| R4-2304118 |
TP to TR 38.877: Phase shifter and antenna |
Nokia, Nokia Shanghai Bell |
| R4-2304627 |
FR2-1 multi-band antenna analysis |
Murata Manufacturing Co Ltd. |
| R4-2304628 |
TP to TR 38.877: Antenna array |
Murata Manufacturing Co Ltd. |
| R4-2304632 |
TP to TR 38.877: Antenna array |
Murata Manufacturing Co Ltd. |
| R4-2304633 |
FR2-1 multi-band antenna analysis |
Murata Manufacturing Co Ltd. |
| R4-2304711 |
TP to TR 38.877: Fractional bandwidth and percentage bandwidth |
NEC |
| R4-2304712 |
TP to TR 38.877: Corrections in DPD sections |
NEC |
| R4-2305301 |
TP on SI summary |
Huawei, HiSilicon |
| R4-2305681 |
Additional feasibility aspects for FR2-1 multi-band BS |
Intel Corporation |
| R4-2305682 |
TP for TR 38.877: Additional feasibility aspects |
Intel Corporation |
| R4-2305880 |
TP to TR 38.877: Antenna array |
Murata Manufacturing Co Ltd. |
| R4-2305881 |
TP to TR 38.877: Fractional bandwidth and percentage bandwidth |
NEC |
| R4-2305884 |
TP on SI summary |
Huawei, HiSilicon, Nokia, Ericsson |
| R4-2305885 |
TP for TR 38.877: Additional feasibility aspects |
Intel Corporation |
| 5.2.3 |
Moderator summary and conclusions |
|
| R4-2305849 |
Topic Summary [106bis-e][302] FS_NR_BS_RF_evo |
Moderator (Globalstar) |
| R4-2305972 |
Topic Summary [106bis-e][302] FS_NR_BS_RF_evo |
Moderator (Globalstar) |
| 5.3.1 |
General and work plan |
|
| R4-2304678 |
3GPP TR 38.871 V0.2.0 |
Qualcomm Incorporated |
| R4-2305787 |
TP to introduce Multi-AoA UE RF Test Aspects |
Keysight Technologies UK Ltd |
| R4-2305886 |
TP to introduce Multi-AoA UE RF Test Aspects |
Keysight Technologies UK Ltd |
| 5.3.2 |
Test methods for RF/RRM/Demodulation requirements |
|
| R4-2304679 |
Discussion on test method for FR2 multi-Rx UE |
Qualcomm Incorporated |
| R4-2304825 |
On multi-RX DL RF test in DL polarization and DCI schemes aspects |
Samsung |
| R4-2305101 |
Discussion on FR2 OTA test method |
vivo |
| R4-2305497 |
Discussion on Test methods |
Huawei,HiSilicon |
| R4-2305609 |
Consideration on 2-AoA reception |
OPPO |
| R4-2305696 |
Test procedure for EIS spherical coverage |
ROHDE & SCHWARZ |
| R4-2305786 |
Testing Considerations for Multi AoA Rx Testing |
Keysight Technologies UK Ltd |
| 5.3.4 |
Moderator summary and conclusions |
|
| R4-2305874 |
Topic Summary [106bis-e][328] FS_NR_FR2_OTA_enh |
Moderator (Qualcomm) |
| R4-2305887 |
WF on FR2 OTA test enhancements SI |
Qualcomm |
| R4-2305997 |
Topic Summary [106bis-e][328] FS_NR_FR2_OTA_enh |
Moderator (Qualcomm) |
| R4-2306200 |
Topic summary for [106-bis-e][121] FS_SimBC |
Moderator (ZTE) |
| R4-2306283 |
Topic summary for [106-bis-e][121] FS_SimBC |
Moderator (ZTE) |
| R4-2306582 |
WF on cross-band isolation MSD simplification for EN-DC |
Skyworks Solutions Inc. |
| R4-2306583 |
WF on MSD simplification due to harmonic and harmonic mixing for EN-DC |
Huawei, HiSilicon |
| R4-2306584 |
WF on handling of the missing fallbacks |
Apple |
| 5.4.1 |
General and work plan |
|
| R4-2304025 |
Text Proposals on study on enhancement for sub-1GHz NR band combinations |
Spark NZ Ltd |
| R4-2305386 |
Work plan for enhancement for sub-1GHz band combinations |
Huawei, HiSilicon, Spark NZ |
| R4-2306589 |
Work plan for enhancement for sub-1GHz band combinations |
Huawei, HiSilicon, Spark NZ |
| 5.4.2.1 |
CA configuration of CA_n5A-n105A |
|
| R4-2304455 |
Considerations on CA_n5-n105 |
Qualcomm Finland RFFE Oy |
| R4-2304560 |
Input on new CA_n5A-n105A band combinations study |
Skyworks Solutions Inc. |
| R4-2305113 |
Discussion on UE architectures and RF requirements impact for CA_n5A-n105A |
vivo |
| R4-2305256 |
Discussion on CA_n5-n105 |
Xiaomi |
| R4-2305387 |
Discussion on RF architecture and potential solution for CA_n5-n105 |
Huawei, HiSilicon, Spark NZ |
| 5.4.2.2 |
CA configuration of CA_n28A-n105A |
|
| R4-2304354 |
CA_n28-n105 UE architecture consideration |
Apple |
| R4-2304456 |
Considerations on CA_n28-n105 |
Qualcomm Finland RFFE Oy |
| R4-2304561 |
Input on new CA_n28A-n105A band combinations study |
Skyworks Solutions Inc. |
| R4-2305114 |
Discussion on UE architectures and RF requirements impact for CA_n28A-n105A |
vivo |
| R4-2305257 |
Discussion on CA_n28-n105 |
Xiaomi |
| R4-2305388 |
Discussion on RF architecture and potential solution for CA_n28-n105 |
Huawei, HiSilicon, Spark NZ |
| R4-2305420 |
Discussion on how to implement CA_n28-n105 |
MediaTek Inc. |
| 5.4.2.3 |
CA configuration of CA_n26A-n28A |
|
| R4-2304457 |
Considerations on CA_n26-n28 |
Qualcomm Finland RFFE Oy |
| R4-2304562 |
Input on new CA_n26A-n28A band combinations study |
Skyworks Solutions Inc. |
| R4-2304613 |
Operator scenario for n26 and n28 spectrum |
Telstra Limited |
| R4-2305115 |
Discussion on UE architectures and RF requirements impact for CA_n26A-n28A |
vivo |
| R4-2305136 |
On CA configuration of CA_n26A-n28A |
ZTE Corporation |
| R4-2305258 |
Discussion on CA_n26-n28 |
Xiaomi |
| R4-2305389 |
Discussion on RF architecture and potential solution for CA_n26-n28 |
Huawei, HiSilicon |
| 5.4.3 |
Moderator summary and conclusions |
|
| R4-2306201 |
Topic summary for [106-bis-e][122] FS_NR_sub1GHz_combo_enh |
Moderator (Huawei) |
| R4-2306284 |
Topic summary for [106-bis-e][122] FS_NR_sub1GHz_combo_enh |
Moderator (Huawei) |
| R4-2306469 |
WF on RF architecture and critical issues for CA_n5-n105 |
Xiaomi |
| R4-2306470 |
WF on RF architecture and critical issues for CA_n28-n105 |
Apple |
| R4-2306471 |
WF on RF architecture and critical issues for CA_n26-n28 |
Huawei, HiSilicon |
| R4-2306472 |
Draft CR for TR 38.872 to introduce the framework for sub-1GHz NR band combinations enhancement |
Spark NZ, Huawei, HiSilicon |
| 5.5.1 |
General and work plan |
|
| R4-2305312 |
Discussion on RRM impacts for further RF requirements enhancement for NR and EN-DC in FR1 |
Huawei, HiSilicon |
| 5.5.2.1 |
4Tx UE RF requirements |
|
| R4-2304161 |
Relation between configured transmitted power and TPMI configuration |
Nokia, Nokia Shanghai Bell |
| R4-2304390 |
4 Tx RF issues |
Qualcomm Technologies Int |
| R4-2304609 |
4Tx UE RF requirements |
LG Electronics |
| R4-2305081 |
Discussion on 4Tx UE RF requirements |
vivo |
| R4-2305295 |
Discussion on 4Tx on for CPE FWA vehicle industrial devices |
Xiaomi |
| R4-2305561 |
On UE RF requirements for 4Tx |
Huawei, HiSilicon |
| R4-2305562 |
draft CR to TS 38.101-1 4Tx requirements (phase 1) |
Huawei, HiSilicon |
| R4-2305707 |
Discussion on FR1 4Tx UE RF requirements |
MediaTek Inc. |
| R4-2305810 |
Input on 4Tx MPR and antenna isolation assumptions |
Skyworks Solutions Inc. |
| R4-2306596 |
draft CR to TS 38.101-1 4Tx requirements (phase 1) |
Huawei, HiSilicon |
| 5.5.2.2 |
8Rx UE RF requirements |
|
| R4-2304186 |
On power imbalance indication due to ?TRxSRS |
Nokia, Nokia Shanghai Bell |
| R4-2304452 |
8RX UE RF requirements |
Qualcomm Finland RFFE Oy |
| R4-2304510 |
Discussion on FR1 8RX UE RF requirements |
Mediatek India Technology Pvt. |
| R4-2305082 |
Discussion on 8Rx UE RF requirements |
vivo |
| R4-2305214 |
Further view on 8Rx for Rel-18 RF FR1 enhancements |
NTT DOCOMO INC. |
| R4-2305294 |
Discussion on 8Rx on for CPE FWA vehicle industrial devices |
Xiaomi |
| R4-2305603 |
On FR1 8Rx UE RF requirements |
Huawei, HiSilicon |
| R4-2305604 |
draft CR for 38.101-1 removal of 3dB relaxation to PCMAX_H,f,c for PC2 capable UE with TxD |
Huawei, HiSilicon |
| R4-2305833 |
Further discussion on 8Rx UE RF requirements in FR1 |
Ericsson Limited |
| R4-2305846 |
On UE Behavior with Delta TRxSRS Power Relaxations |
Lenovo |
| 5.5.2.3 |
Lower MSD for inter-band CA/EN-DC/DC combinations |
|
| R4-2305365 |
Views on lower MSD signaling and UE RF requirements |
Apple |
| R4-2305563 |
TR 38.881 v0.4.0 |
Huawei, HiSilicon |
| 5.5.2.3.1 |
Study of approach for UE indication and signaling design |
|
| R4-2304094 |
Views on lower MSD signaling |
Nokia, Nokia Shanghai Bell |
| R4-2304182 |
Updated the lower MSD capability signalling |
Meta Ireland |
| R4-2304188 |
TP for TR 38.881 update of MSD 0 dB region approach |
Nokia, Nokia Shanghai Bell |
| R4-2304202 |
discussion on MSD capability |
CMCC |
| R4-2304389 |
Signalling for low MSD |
Qualcomm Technologies Int |
| R4-2304520 |
On the signalling design for low-MSD capability |
Huawei, HiSilicon |
| R4-2304521 |
TP for TR 38.881 on the signalling design for low-MSD capability |
Huawei, HiSilicon |
| R4-2304663 |
Discussion for lower MSD threshold |
LG Electronics France |
| R4-2304717 |
Views on signalling design for lower MSD |
Samsung |
| R4-2304870 |
Discussion on possible Lower MSD signalling approaches |
MediaTek Inc. |
| R4-2305083 |
Discussion of lower MSD Signalling |
vivo |
| R4-2305130 |
On lower MSD for inter-band CA/ENDC |
ZTE Corporation |
| R4-2305296 |
Discussion on lower MSD signaling for inter-band CA/EN-DC/DC |
Xiaomi |
| R4-2305564 |
draft LS on lower MSD capability |
Huawei, HiSilicon |
| R4-2305573 |
Discussion on the information needed in the Lower MSD capability |
CHTTL |
| R4-2305656 |
Input on improved MSD signaling and requirement |
Skyworks Solutions Inc. |
| R4-2306592 |
TP for TR 38.881 update of MSD 0 dB region approach |
Nokia, Nokia Shanghai Bell |
| R4-2306593 |
TP for TR 38.881 on the signalling design for low-MSD capability |
Huawei, HiSilicon |
| R4-2306594 |
LS on lower MSD capability |
Huawei, HiSilicon |
| 5.5.2.3.2 |
UE RF requirements for lower MSD |
|
| R4-2304187 |
Lower MSD requirements handling |
Nokia, Nokia Shanghai Bell |
| R4-2304718 |
Views on UE RF requirements for lower MSD |
Samsung |
| 5.5.3.1 |
RLM test cases to support 8Rx |
|
| R4-2305313 |
Discussion on RLM/BFD test case for 8Rx capable UEs |
Huawei, HiSilicon |
| 5.5.4.1 |
8Rx UE demodulation and CSI |
|
| R4-2304158 |
On PDSCH demodulation requirements for 8Rx for NR and EN-DC in FR1 |
Apple |
| R4-2304880 |
8Rx for CPE/FWA/vehicle/industrial devices: Demodulation requirements |
Qualcomm India Pvt Ltd |
| 5.5.4.1.1 |
PDSCH requirements |
|
| R4-2304097 |
Discussion on 8Rx UE demodulation requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304098 |
Simulation results for 8Rx UE demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2304666 |
Discussion on 8Rx UE demodulation and CSI |
ZTE Corporation |
| R4-2304688 |
Discussion on demodulation requirements for UEs supporting multiple Rx |
China Telecom |
| R4-2304899 |
discussion on 8Rx PDSCH requirements |
Samsung |
| R4-2304900 |
simulation results on 8Rx UE demodulation requirements |
Samsung |
| R4-2304914 |
Discussion on PDSCH requirements for 8Rx UE |
MediaTek inc. |
| R4-2305462 |
Discussions on PDSCH requirements and applicability rules for 8Rx |
Huawei,HiSilicon |
| R4-2305508 |
Remaining issues on PDSCH requirements for 8 Rx in FR1 |
Ericsson |
| R4-2305509 |
Simulation results for 8 Rx PDSCH requirements in FR1 |
Ericsson |
| 5.5.4.1.2 |
SDR requirements |
|
| R4-2304101 |
Discussion on 8Rx SDR requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304901 |
discussion and simulation results on 8Rx SDR requirements |
Samsung |
| R4-2304915 |
Discussion on SDR requirements for 8Rx UE |
MediaTek inc. |
| R4-2305463 |
Discussions on SDR requirements for 8Rx |
Huawei,HiSilicon |
| R4-2305510 |
Remaining issues on SDR requirements for 8 Rx in FR1 |
Ericsson |
| R4-2305511 |
Simulation results for 8 Rx SDR in FR1 |
Ericsson |
| 5.5.4.1.3 |
CQI reporting requirements |
|
| R4-2304099 |
Discussion on 8Rx CSI requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304100 |
Simulation results for 8Rx CSI requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304667 |
Discussion on 8Rx CQI reporting requirements |
ZTE Corporation |
| R4-2304916 |
Discussion on CQI requirements for 8Rx UE |
MediaTek inc. |
| R4-2305464 |
Discussions on CQI requirements for 8Rx |
Huawei,HiSilicon |
| R4-2305512 |
Remaining issues on CQI reporting for 8Rx in FR1 |
Ericsson |
| R4-2305513 |
Simulation results for CQI reporting for 8Rx in FR1 |
Ericsson |
| 5.5.4.2 |
4Tx BS demodulation |
|
| R4-2304047 |
Discussion on 4Tx BS Demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2304048 |
Supporting results for 4Tx Demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2304159 |
On SDR demodulation requirements for 8Rx for NR and EN-DC in FR1 |
Apple |
| R4-2304398 |
Discussion on 4Tx BS dmodulation requirements |
Ericsson |
| R4-2304399 |
Simulation on 4Tx BS dmodulation requirements |
Ericsson |
| R4-2304690 |
Discussion on demodulation for 4Tx of NR_ENDC_RF_FR1 |
ZTE Corporation |
| R4-2305465 |
Discussions on 4Tx BS requirements |
Huawei,HiSilicon |
| R4-2305466 |
Simulation results on 4Tx BS requirements |
Huawei,HiSilicon |
| R4-2305543 |
Discussion and initial simulation results for PUSCH with UL 4-layer transmission |
Samsung |
| 5.5.5 |
Moderator summary and conclusions |
|
| R4-2305863 |
Topic Summary [106bis-e][317] RF_FR1_enh2_Demod_Part1 |
Moderator (Huawei) |
| R4-2305864 |
Topic Summary [106bis-e][318] RF_FR1_enh2_Demod_Part2 |
Moderator (Ericsson) |
| R4-2305888 |
WF on 8Rx demodulation and CSI requirements |
Huawei |
| R4-2305889 |
Summary of simulation results for 8Rx demodulation requirements |
Huawei |
| R4-2305890 |
WF on FR1 4Tx demodulation requirement |
Ericsson |
| R4-2305986 |
Topic Summary [106bis-e][317] RF_FR1_enh2_Demod_Part1 |
Moderator (Huawei) |
| R4-2305987 |
Topic Summary [106bis-e][318] RF_FR1_enh2_Demod_Part2 |
Moderator (Ericsson) |
| R4-2306149 |
Topic summary for [106-bis-e][201] NR_ENDC_ RF_FR1_enh2 |
Moderator (NTT Docomo) |
| R4-2306202 |
Topic summary for [106-bis-e][123] FR1_enh2_part1 |
Moderator (Huawei) |
| R4-2306203 |
Topic summary for [106-bis-e][124] FR1_enh2_part2 |
Moderator (Vivo) |
| R4-2306204 |
Topic summary for [106-bis-e][125] FR1_enh2_part3 |
Moderator (NTT Docomo) |
| R4-2306232 |
Topic summary for [106-bis-e][201] NR_ENDC_ RF_FR1_enh2 |
Moderator (NTT Docomo) |
| R4-2306285 |
Topic summary for [106-bis-e][123] FR1_enh2_part1 |
Moderator (Huawei) |
| R4-2306286 |
Topic summary for [106-bis-e][124] FR1_enh2_part2 |
Moderator (Vivo) |
| R4-2306287 |
Topic summary for [106-bis-e][125] FR1_enh2_part3 |
Moderator (NTT Docomo) |
| R4-2306317 |
WF on RRM performance requirements for Further RF requirements enhancement for NR and EN-DC in FR1 |
NTT DOCOMO, INC. |
| R4-2306590 |
WF on lower MSD |
Huawei, HiSilicon |
| R4-2306591 |
LS on clarification of test configurations for CA/DC MSD requirements |
Samsung |
| R4-2306595 |
WF on 4Tx UE RF requirements |
Vivo |
| R4-2306597 |
WF on UE RF for 8Rx |
NTT DOCOMO, INC. |
| 5.6.1 |
General and work plan |
|
| R4-2304462 |
Work plan for the WI on channel raster enhancement |
Ericsson |
| R4-2306599 |
Work plan for the WI on channel raster enhancement |
Ericsson |
| 5.6.2 |
UE and BS channel raster |
|
| R4-2304262 |
Views on the UE channel raster for FR1 |
Intel Corporation |
| R4-2304263 |
Clarification of UE capability enhancement of channel raster in bands below 3GHz |
Intel Corporation |
| R4-2304264 |
Clarification of UE capability enhancement of channel raster in bands below 3GHz |
Intel Corporation |
| R4-2304265 |
Clarification of UE capability enhancement of channel raster in bands below 3GHz |
Intel Corporation |
| R4-2304266 |
Clarification of UE capability enhancement of channel raster in bands below 3GHz |
Intel Corporation |
| R4-2304334 |
Initial considerations for the flexible channel raster |
Apple |
| R4-2304335 |
Flexible channel raster for the NTN bands |
Apple |
| R4-2304463 |
On changing the BS and UE channel raster |
Ericsson |
| R4-2304653 |
Discussion on UE and BS channel raster |
CMCC |
| R4-2304664 |
Discussion on channel raster for SIB1 CBW and UE-specific CBW |
China Telecom |
| R4-2304876 |
Discussion on channel raster enhancement |
Nokia, Nokia Shanghai Bell |
| R4-2305308 |
Discussion on Channel raster enhancement |
Huawei, HiSilicon |
| R4-2305353 |
Discussion on channel raster enhancement |
ZTE Corporation |
| R4-2305517 |
Channel Raster Enhancements |
Qualcomm Incorporated |
| R4-2305559 |
Discussion on Channel raster enhancement |
Huawei, HiSilicon |
| R4-2305585 |
Channel raster enhancement |
Samsung Electronics Co., Ltd |
| R4-2305702 |
Consideration on channel raster enhancement |
MediaTek Inc. |
| R4-2305828 |
10 kHz raster for bands that currently specify the 100 kHz raster |
T-Mobile USA |
| 5.6.3 |
UE capability |
|
| R4-2304336 |
UE capability for the flexible channel raster |
Apple |
| R4-2304464 |
On a UE capability for channel raster enhancement |
Ericsson |
| R4-2304654 |
Discussion on UE capability of new channel raster |
CMCC |
| R4-2304877 |
Discussion on UE capability for channel raster enhancement |
Nokia, Nokia Shanghai Bell |
| R4-2305560 |
UE capability for channel raster enhancement |
Huawei, HiSilicon |
| R4-2305703 |
Consideration on enhanced channel raster capability |
MediaTek Inc. |
| 5.6.4 |
Moderator summary and conclusions |
|
| R4-2306205 |
Topic summary for [106-bis-e][126] NR_channel_raster_enh |
Moderator (Ericsson) |
| R4-2306288 |
Topic summary for [106-bis-e][126] NR_channel_raster_enh |
Moderator (Ericsson) |
| R4-2306598 |
WF on channel raster enhancement |
Ericsson |
| 5.7.1 |
General and work plan |
|
| R4-2305066 |
TR38.891 v 0.4.0 for NR RF requirements enhancement for frequency range 2 (FR2), Phase 3 |
Xiaomi,Nokia |
| 5.7.2 |
UL 256QAM |
|
| R4-2304119 |
Proposals on UE RF requirements for FR2-1 UL 256QAM |
Nokia, Nokia Shanghai Bell |
| R4-2304327 |
On FR2 UL 256QAM |
Apple |
| R4-2304601 |
On enabling FR2 UL256QAM |
Qualcomm Incorporated |
| R4-2304634 |
MPR evaluation results for FR2-1 UL256QAM PC1 and PC2 |
LG Electronics France |
| R4-2304689 |
Discussion on FR2-1 UL 256QAM |
ZTE Corporation |
| R4-2304699 |
Views on FR2-1 UL 256QAM |
MediaTek Korea Inc. |
| R4-2305067 |
TP for TR 38.891 on link level simulation results and system level simulation assumption for FR2 UL 256QAM |
Xiaomi |
| R4-2305068 |
Discussion on UL 256QAM |
Xiaomi |
| R4-2305093 |
Discussion on FR2 UL 256QAM |
vivo |
| R4-2305309 |
UE UL 256QAM |
Huawei, HiSilicon |
| R4-2305691 |
UL 256QAM, phase noise profiles and EVM testing |
Anritsu Limited |
| R4-2305745 |
Views on UL 256-QAM for FR2-1 |
Sony |
| R4-2305835 |
Discussion on UL 256QAM UE RF requirements for FR2-1 |
Ericsson Limited |
| 5.7.3 |
Beam correspondence requirements for RRC_INACTIVE and initial access |
|
| R4-2304312 |
Introducing beam correspondence requirement for IA/RA-SDT/CG-SDT |
Apple |
| R4-2304313 |
Revised WID: NR RF requirements enhancement for frequency range 2 (FR2), Phase 3 |
Apple |
| R4-2305747 |
Views on Beam correspondence for initial access |
Sony, Ericsson |
| 5.7.3.1 |
Beam correspondence requirement applicability |
|
| R4-2304197 |
Beam correspondence requirements for initial access |
CMCC |
| R4-2304310 |
Beam correspondence requirement for IA/RA-SDT/CG-SDT |
Apple |
| R4-2304473 |
Beam correspondence requirement applicability |
Nokia, Nokia Shanghai Bell |
| R4-2304625 |
TP for TR 38.891: General and Specification impact |
Apple |
| R4-2304629 |
On beam correspondence requirements |
Huawei, HiSilicon |
| R4-2304826 |
Thoughts on breakthrough of FR2 beam correspondence in initial access |
Samsung |
| R4-2305069 |
Discussion on beam correspondence requirements for RRC_INACTIVE and initial access |
Xiaomi |
| R4-2305094 |
Discussion on beam correspondence requirement applicability |
vivo |
| R4-2305352 |
Discussion on beam correspondence requirement applicability |
ZTE Corporation |
| R4-2305683 |
Requirement applicability for RRC_INACTIVE and initial access |
Intel Corporation |
| R4-2305704 |
On beam correspondence requirement applicability for initial access and RRC_INACTIVE mode |
MediaTek Inc. |
| R4-2306602 |
TP for TR 38.891: General and Specification impact |
Apple, Nokia, Nokia Shanghai Bell |
| 5.7.3.2 |
UE beam type and DRX implications |
|
| R4-2304474 |
UE beam type and DRX implicationss |
Nokia, Nokia Shanghai Bell |
| R4-2305095 |
Discussion on beam type and requirement of beam correspondence |
vivo |
| R4-2305705 |
On UE beam type and DRX implications |
MediaTek Inc. |
| R4-2306601 |
UE beam type and DRX implicationss |
Nokia, Nokia Shanghai Bell |
| 5.7.3.3 |
Beam correspondence test issues |
|
| R4-2304198 |
Beam correspondence test issues for initial access state |
CMCC |
| R4-2304311 |
Further consideration on test issue for beam correspondence |
Apple |
| R4-2304314 |
LS on testing for beam correspondence |
Apple |
| R4-2304475 |
Beam correspondence test issues |
Nokia, Nokia Shanghai Bell |
| R4-2304602 |
On UBF for initial access beam correspondence |
Qualcomm Incorporated |
| R4-2304626 |
TP for TR 38.891: Testing impact |
Apple |
| R4-2304630 |
On beam correspondence test issues |
Huawei, HiSilicon |
| R4-2304827 |
Further reply LS on testability for beam correspondence in initial access |
Samsung |
| R4-2305070 |
Discussion on beam correspondence test for RRC_INACTIVE and initial access |
Xiaomi |
| R4-2305096 |
Discussion on beam correspondence test related issue |
vivo |
| R4-2305706 |
On Beam correspondence test issues |
MediaTek Inc. |
| 5.7.4 |
Moderator summary and conclusions |
|
| R4-2306206 |
Topic summary for [106-bis-e][127] FR2_enh_req_Ph3_part1 |
Moderator (Nokia) |
| R4-2306207 |
Topic summary for [106-bis-e][128] FR2_enh_req_Ph3_part2 |
Moderator (Xiaomi) |
| R4-2306289 |
Topic summary for [106-bis-e][127] FR2_enh_req_Ph3_part1 |
Moderator (Nokia) |
| R4-2306290 |
Topic summary for [106-bis-e][128] FR2_enh_req_Ph3_part2 |
Moderator (Xiaomi) |
| R4-2306600 |
WF on beam correspondence in initial access and RRC_INACTIVE |
Nokia |
| R4-2306603 |
WF on FR2-1 UL 256 QAM |
Xiaomi |
| 5.8.2 |
UE RF requirements for simultaneous DL reception with up to 4 layer MIMO |
|
| R4-2305599 |
On UE RF requirement for FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| R4-2305750 |
Further views on multi-Rx chain DL reception in FR2 |
Sony, Ericsson |
| 5.8.2.1 |
System parameter assumption, UE architecture and conditions of UE RF requirements |
|
| R4-2304120 |
Discussion on System parameter assumption, UE architecture and conditions of UE RF requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304129 |
System parameter and UE assumption for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2304163 |
Discussion on simulation assumption for FR2-1 multi-Rx |
Murata Manufacturing Co Ltd. |
| R4-2305097 |
Discussion on system parameters of multi-Rx DL reception |
vivo |
| R4-2305611 |
On AoA separation |
OPPO |
| 5.8.2.2 |
UE RF requirements |
|
| R4-2304121 |
Proposal on UE RF requirements for FR2-1 multi-Rx chain DL reception |
Nokia, Nokia Shanghai Bell |
| R4-2304130 |
RF requirement for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2304603 |
On UE RF requirements for 2AoA FR2 DL MIMO |
Qualcomm Incorporated |
| R4-2304608 |
Discussion on UE RF requirements for simultaneous DL reception |
LG Electronics |
| R4-2304797 |
Discussion on UE RF requirements for simultaneous DL reception |
ZTE Corporation |
| R4-2304824 |
FR2 Multi-RX 2AoA spherical coverage simulation and requirements |
Samsung |
| R4-2305071 |
Discussion on UE RF requirements supporting simultaneous DL reception |
Xiaomi |
| R4-2305098 |
Further evaluation on multi-Rx DL reception |
vivo |
| R4-2305616 |
On the RF requirement of multi DL reception |
OPPO |
| R4-2305788 |
On UE RF Requirements for Multi-AoA Rx Testing |
Keysight Technologies UK Ltd |
| 5.8.3.1 |
General aspects |
|
| R4-2304051 |
Discussion on general RRM aspects for multi Rx |
Nokia, Nokia Shanghai Bell |
| R4-2304131 |
On general aspects for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2304242 |
Discussion on FR2 multi Rx chain general aspects |
Intel Corporation |
| R4-2304369 |
Conditions of UE multiple Rx-beam based DL reception |
Qualcomm Korea |
| R4-2304706 |
Discussion on general aspects of RRM for FR2 multi-Rx chains |
LG Electronics Inc. |
| R4-2304995 |
Discussion on general aspects on RRM requirements for simultaneous DL reception from different directions |
ZTE Corporation |
| R4-2305040 |
On general aspects for FR2 multi-Rx |
vivo |
| R4-2305161 |
Discussion on general aspects for multi-Rx UEs |
MediaTek inc. |
| R4-2305196 |
General aspects discussions for FR2 multi Rx chain DL reception |
NTT DOCOMO, INC. |
| R4-2305208 |
Discussion on general aspects for FR2 multi-RX DL reception |
Samsung |
| R4-2305228 |
On general aspects for FR2_multiRX_DL |
OPPO |
| R4-2305268 |
Discussion on general aspects for NR FR2 multi-Rx |
Huawei, HiSilicon |
| R4-2305768 |
On general aspects |
Ericsson |
| 5.8.3.2 |
L1-RSRP measurement delay |
|
| R4-2304052 |
Discussion on MultiRx L1 measurements |
Nokia, Nokia Shanghai Bell |
| R4-2304132 |
On L1 measurements for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2304243 |
Discussion on RRM impacts for L1 measurement based on FR2 multi Rx chain |
Intel Corporation |
| R4-2304370 |
L1 measurement requirements for support of simultaneous receptions from two TRPs |
Qualcomm Korea |
| R4-2304708 |
Discussion on L1-RSRP measurement for FR2 multi-Rx chains |
LG Electronics Inc. |
| R4-2304789 |
on the L1-RSRP measurement delay |
Xiaomi |
| R4-2304855 |
Discussion on L1-RSRP measurement delay for FR2 multi-Rx chain DL reception |
CMCC |
| R4-2304996 |
Discussion on L1-RSRP measurement requirements for simultaneous DL reception from different directions |
ZTE Corporation |
| R4-2305041 |
On L1-RSRP measurement delay for multi-Rx |
vivo |
| R4-2305162 |
Discussion on L1 measurements for multi-Rx UEs |
MediaTek inc. |
| R4-2305209 |
Discussion on L1-RSRP measurement delay for FR2 multi-RX DL reception |
Samsung |
| R4-2305229 |
On L1 measurement for FR2_multiRX_DL |
OPPO |
| R4-2305314 |
Discussion on L1-RSRP measurements for R18 FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| R4-2305769 |
On L1-RSRP measurements |
Ericsson |
| 5.8.3.3 |
RLM and BFD/CBD requirements |
|
| R4-2304049 |
On Multi Rx RLM and BFD/CBD requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304133 |
On RLM and BFD/CBD for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2304244 |
Discussion on RRM impacts for RLM BFD on FR2 multi Rx chain |
Intel Corporation |
| R4-2304371 |
RLM and BM requirements for sDCI |
Qualcomm Korea |
| R4-2304790 |
on the RLM and BFD CBD requirement |
Xiaomi |
| R4-2304982 |
Discussion on RLM/BFD/CBD requirements for FR2 multi-Rx chain DL reception |
CMCC |
| R4-2304997 |
Discussion on RLM, BFD and CBD for simultaneous DL reception from different directions |
ZTE Corporation |
| R4-2305042 |
On RLM and BFD/CBD requiremets for FR2 multi-Rx |
vivo |
| R4-2305163 |
Discussion on RLM/BFD/CBD for multi-Rx UEs |
MediaTek inc. |
| R4-2305197 |
BFD/CBD requirements for FR2 multi Rx chain DL reception |
NTT DOCOMO, INC. |
| R4-2305210 |
Discussion on RLM and BFD/CBD requirements for FR2 multi-RX DL reception |
Samsung |
| R4-2305315 |
Discussion on RLM and BFD/CBD measurements for R18 FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| R4-2305770 |
On RLM and beam management |
Ericsson |
| 5.8.3.4 |
Scheduling/measurement restrictions |
|
| R4-2304053 |
Discussion on MultiRx scheduling restrictions |
Nokia, Nokia Shanghai Bell |
| R4-2304152 |
On scheduling/measurement restrictions for multiple Rx chains |
Apple |
| R4-2304245 |
Discussion on RRM impacts for scheduling/measurement restriction on FR2 multi Rx chain |
Intel Corporation |
| R4-2304372 |
SSB based scheduling and measurement restrictions |
Qualcomm Korea |
| R4-2304707 |
Discussion on scheduling restriction for FR2 multi-Rx chains |
LG Electronics Inc. |
| R4-2304791 |
on the scheduling measurement restrictions |
Xiaomi |
| R4-2304856 |
Discussion on scheduling/measurement restrictions for FR2 multi-Rx chain DL reception |
CMCC |
| R4-2304998 |
Discussion on scheduling restriction and measurement restriction for simultaneous DL reception from different directions |
ZTE Corporation |
| R4-2305043 |
On scheduling and measurement restrictions for multi-Rx |
vivo |
| R4-2305164 |
Discussion on scheduling and measurement restriction for multi-Rx UEs |
MediaTek inc. |
| R4-2305230 |
On measurement restriction for FR2_multiRX_DL |
OPPO |
| R4-2305316 |
Discussion on scheduling/measurement restrictions for R18 FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| R4-2305434 |
Discussion on scheduling/measurement restrictions for FR2 multi-RX DL reception |
Samsung |
| R4-2305754 |
Discussion on Scheduling and measurement restrictions |
Ericsson |
| 5.8.3.5 |
TCI state switching delay with dual TCI |
|
| R4-2304050 |
On Multi Rx TCI state switching requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304134 |
On TCI state switching for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2304246 |
Discussion on TCI state switching requirement based on FR2 multi Rx chain |
Intel Corporation |
| R4-2304373 |
TCI and UE beam switching delay requirements |
Qualcomm Korea |
| R4-2304792 |
on the TCI state switching delay with dual TCI |
Xiaomi |
| R4-2305044 |
On TCI state switching delay for multi-Rx |
vivo |
| R4-2305165 |
Discussion on dual TCI state switch for multi-Rx UEs |
MediaTek inc. |
| R4-2305231 |
On TCI state switching for FR2 multi-Rx DL |
OPPO |
| R4-2305269 |
Discussion on TCI state switching delay with dual TCI for NR FR2 multi-Rx |
Huawei, HiSilicon |
| R4-2305755 |
Discussion on TCI state switching delay with dual TCI |
Ericsson |
| 5.8.3.6 |
Receive timing difference between different directions |
|
| R4-2304054 |
Discussion on Receive timing difference between different directions |
Nokia, Nokia Shanghai Bell |
| R4-2304793 |
on the RTD between different directions |
Xiaomi |
| R4-2304833 |
On timing issues for multi RX in FR2 |
Ericsson |
| R4-2304999 |
Discussion on Receive timing difference between different directions |
ZTE Corporation |
| R4-2305166 |
Discussion on receive timing difference for multi-Rx UEs |
MediaTek inc. |
| R4-2305270 |
Discussion on receiving timing difference between different directions for NR FR2 multi-Rx |
Huawei, HiSilicon |
| 5.8.4 |
Demodulation performance and CSI requirements |
|
| R4-2305118 |
Discussion on FR2 Multi-Rx DL Demod |
MediaTek inc. |
| 5.8.4.1 |
General aspects |
|
| R4-2304104 |
On MultiRx Demodulation performance and CSI requirements - General aspects |
Nokia, Nokia Shanghai Bell |
| R4-2304135 |
On General aspects for Multi-RX in FR2 requirements |
Apple |
| R4-2304258 |
General aspects on NR FR2 multi-Rx DL demodulation |
Intel Corporation |
| R4-2304394 |
Views on General Aspects for FR2 Multi-Rx |
Qualcomm Incorporated |
| R4-2305479 |
Discussion on general issues for UE demodulation requirements for NR FR2 multi-Rx chain DL reception |
Huawei,HiSilicon |
| R4-2305514 |
General aspects for FR2 multi-Rx DL chain |
Ericsson |
| R4-2305878 |
General aspects on NR FR2 multi-Rx DL demodulation |
Intel Corporation |
| 5.8.4.2 |
PDSCH requirements |
|
| R4-2304105 |
On MultiRx Demodulation performance and CSI requirements - PDSCH |
Nokia, Nokia Shanghai Bell |
| R4-2304136 |
On PDSCH demodulation requirements with multi-RX in FR2 |
Apple |
| R4-2304395 |
Views on PDSCH Performance Requirements for FR2 Multi-Rx |
Qualcomm Incorporated |
| R4-2305003 |
Views on NR FR2 multi-Rx chain DL reception requirements for PDSCH |
NTT DOCOMO, INC. |
| R4-2305481 |
Discussion on UE PDSCH demodulation requirements for NR FR2 multi-Rx chain DL reception |
Huawei,HiSilicon |
| R4-2305482 |
Simulation results on UE PDSCH demodulation requirements for NR FR2 multi-Rx chain DL reception |
Huawei,HiSilicon |
| R4-2305515 |
PDSCH demodulation requirements for FR2 multi-Rx chain |
Ericsson |
| 5.8.4.3 |
PMI reporting requirements |
|
| R4-2304106 |
On MultiRx Demodulation performance and CSI requirements - PMI |
Nokia, Nokia Shanghai Bell |
| R4-2304137 |
On PDSCH PMI reporting requirements with multi-RX in FR2 |
Apple |
| R4-2304393 |
Views on PMI Reporting Requirements for FR2 Multi-Rx |
Qualcomm Incorporated |
| R4-2305480 |
Discussion on UE CSI reporting requirements for NR FR2 multi-Rx chain DL reception |
Huawei,HiSilicon |
| R4-2305516 |
PMI reporting for FR2 multi-Rx DL reception |
Ericsson |
| 5.8.5 |
Moderator summary and conclusions |
|
| R4-2305865 |
Topic Summary [106bis-e][319] NR_FR2_multiRX_DL_Demod |
Moderator (Qualcomm) |
| R4-2305988 |
Topic Summary [106bis-e][319] NR_FR2_multiRX_DL_Demod |
Moderator (Qualcomm) |
| R4-2306000 |
WF on UE demodulation and CSI requirements for FR2 Multi-Rx reception |
Qualcomm |
| R4-2306150 |
Topic summary for [106-bis-e][202] FR2_multiRx_part1 |
Moderator (Vivo) |
| R4-2306151 |
Topic summary for [106-bis-e][203] FR2_multiRx_part2 |
Moderator (Ericsson) |
| R4-2306208 |
Topic summary for [106-bis-e][129] FR2_multiRx_UERF_part1 |
Moderator (Qualcomm) |
| R4-2306209 |
Topic summary for [106-bis-e][130] FR2_multiRx_UERF_part2 |
Moderator (Apple) |
| R4-2306233 |
Topic summary for [106-bis-e][202] FR2_multiRx_part1 |
Moderator (Vivo) |
| R4-2306234 |
Topic summary for [106-bis-e][203] FR2_multiRx_part2 |
Moderator (Ericsson) |
| R4-2306291 |
Topic summary for [106-bis-e][129] FR2_multiRx_UERF_part1 |
Moderator (Qualcomm) |
| R4-2306292 |
Topic summary for [106-bis-e][130] FR2_multiRx_UERF_part2 |
Moderator (Apple) |
| R4-2306318 |
WF on NR FR2 multi-Rx chain DL reception RRM requirements (part 1) |
Vivo |
| R4-2306319 |
WF on NR FR2 multi-Rx chain DL reception RRM requirements (part 2) |
Ericsson |
| R4-2306320 |
LS on RS supported for group-based reporting |
Ericsson |
| R4-2306392 |
Topic summary for [106-bis-e][202] FR2_multiRx_part1 |
Moderator (Vivo) |
| R4-2306394 |
LS on RS supported for group-based reporting |
Ericsson |
| R4-2306397 |
WF on completion of specification support for BWP operation without restriction |
Vivo |
| R4-2306604 |
WF on FR2-1 UERF requirements for FR2 multi-Rx |
Vivo |
| 5.9.2.1 |
L3 part enhancement for FR2 SCell activation |
|
| R4-2304147 |
On L3 part enhancement for FR2 SCell activation |
Apple |
| R4-2304177 |
L3 part enhancement on FR2 SCell activation delay reduction |
Nokia, Nokia Shanghai Bell |
| R4-2304240 |
Discussion on L3 part enhancement for FR2 SCell activation |
Intel Corporation |
| R4-2304377 |
Discussion on L3 part enhancement for FR2 SCell activation |
Qualcomm Incorporated |
| R4-2304620 |
Discussion on L3 part enhancement for FR2 SCell activation |
MediaTek inc. |
| R4-2304704 |
Discussion on L3 enhancement for FR2 SCell activation delay reduction |
LG Electronics Inc. |
| R4-2304761 |
Discussion on L3 part enhancement for FR2 SCell activation |
Xiaomi |
| R4-2304806 |
Discussion on L3 aspects of FR2 SCell activation enhancements |
vivo |
| R4-2304842 |
Discussion on L3 part enhancement for FR2 SCell activation |
CMCC |
| R4-2304989 |
Discussion on the L3 part enhancement of RRM requirements for FR2 SCell activation delay reduction |
ZTE Corporation |
| R4-2305021 |
Discussion on L3 part enhancement for FR2 SCell activation |
China Telecom |
| R4-2305232 |
Discussion on L3 enhancement for FR2 Scell activation delay reduction |
OPPO |
| R4-2305264 |
Discussion on L3 enhancement for FR2 SCell activation delay reduction |
Huawei, HiSilicon |
| R4-2305756 |
On FR2 SCell activation delay reduction: L3 aspects |
Ericsson |
| 5.9.2.2 |
L1 part enhancement for FR2 SCell activation |
|
| R4-2304148 |
On L1 part enhancement for FR2 SCell activation |
Apple |
| R4-2304178 |
L1 part enhancement on FR2 SCell activation delay reduction |
Nokia, Nokia Shanghai Bell |
| R4-2304241 |
Discussion on L1 part enhancement for FR2 SCell activation |
Intel Corporation |
| R4-2304378 |
Discussion on L1 part enhancement for FR2 SCell activation |
Qualcomm Incorporated |
| R4-2304621 |
Discussion on L1 part enhancement for FR2 SCell activation |
MediaTek inc. |
| R4-2304705 |
Discussion on L1 enhancement for FR2 SCell activation delay reduction |
LG Electronics Inc. |
| R4-2304762 |
Discussion on L1 part enhancement for FR2 SCell activation |
Xiaomi |
| R4-2304807 |
Discussion on L1 aspects of FR2 SCell activation enhancements |
vivo |
| R4-2304843 |
Discussion on L1 part enhancement for FR2 SCell activation |
CMCC |
| R4-2304988 |
Discussion on the L1 part enhancement of RRM requirements for FR2 SCell activation delay reduction |
ZTE Corporation |
| R4-2305022 |
Discussion on L1 part enhancement for FR2 SCell activation |
China Telecom |
| R4-2305168 |
Discussion on L1 part enhancement for FR2 SCell activation |
NTT DOCOMO, INC. |
| R4-2305233 |
Discussion on L1 enhancement for FR2 Scell activation delay reduction |
OPPO |
| R4-2305265 |
Discussion on L1 enhancement for FR2 SCell activation delay reduction |
Huawei, HiSilicon |
| R4-2305757 |
On FR2 SCell activation delay reduction: L1 RSRP |
Ericsson |
| 5.9.2.3 |
Other enhancements for FR2 SCell activation |
|
| R4-2304149 |
On other potential enhancement for FR2 SCell activation |
Apple |
| R4-2304179 |
Other enhancements on FR2 SCell activation delay reduction |
Nokia, Nokia Shanghai Bell |
| R4-2304379 |
Discussion on other enhancement for FR2 SCell activation |
Qualcomm Incorporated |
| R4-2304808 |
LS on the measurement and report mechanism for SCell activation delay reduction |
vivo |
| R4-2304987 |
Discussion on other aspects of RRM requirements enhancement for FR2 SCell activation delay reduction |
ZTE Corporation |
| R4-2305234 |
Discussion on other enhancements for FR2 Scell activation delay reduction |
OPPO |
| R4-2305266 |
Discussion on FR2 SCell activation enhancement |
Huawei, HiSilicon |
| R4-2305758 |
On FR2 SCell activation delay reduction: Others |
Ericsson |
| 5.9.3 |
RRM core requirements for FR1-FR1 NR-DC |
|
| R4-2304150 |
On RRM requirements for FR1-FR1 NR-DC |
Apple |
| R4-2304380 |
DraftCR applicability Rule for FR1+FR1 |
Qualcomm Incorporated |
| R4-2304381 |
DraftCR Scheduling availability for FR1+FR1 |
Qualcomm Incorporated |
| R4-2304622 |
Draft CR for FR1-FR1 NR-DC on scheduling availability of UE during candidate beam detection |
MediaTek inc. |
| R4-2304696 |
DraftCR on scheduling availability during L1-RSRP measurement for FR1-FR1 NR-DC |
Nokia, Nokia Shanghai Bell |
| R4-2304697 |
discussion on FR1-FR1 NR-DC |
Nokia, Nokia Shanghai Bell |
| R4-2304773 |
Discussion on RRM core requirements for FR1-FR1 NR-DC |
Xiaomi |
| R4-2304774 |
Draft CR on HO with PSCell requirements for FR1-FR1 NR-DC |
Xiaomi |
| R4-2304897 |
Discussion on FR1-FR1 NR-DC RRM requirements |
Ericsson |
| R4-2304898 |
draft CR for Rel-18 eFeRRM NR-DC FR1-FR1 SCG activation |
Ericsson |
| R4-2305056 |
Discussion on RRM core requirements for FR1-FR1 NR-DC |
vivo |
| R4-2305057 |
Draft CR on PSCell addition/release delay for FR1+FR1 NR-DC |
vivo |
| R4-2305235 |
Discussion on remaining issues of RRM requirements for FR1+FR1 NR-DC |
OPPO |
| R4-2305236 |
Draft CR on CSSF requirements for FR1+FR1 NR-DC |
OPPO |
| R4-2305237 |
Draft CR on scheduling availability of UE during beam failure detection for FR1+FR1 NR-DC |
OPPO |
| R4-2305238 |
Draft CR on scheduling availability of UE during intra-frequency measurements for FR1+FR1 NR-DC |
OPPO |
| R4-2305267 |
Discussion on NR-DC requirements in Rel-18 |
Huawei, HiSilicon |
| R4-2306323 |
DraftCR Scheduling availability for FR1+FR1 |
Qualcomm Incorporated |
| R4-2306324 |
Draft CR for FR1-FR1 NR-DC on scheduling availability of UE during candidate beam detection |
MediaTek inc. |
| R4-2306325 |
DraftCR on scheduling availability during L1-RSRP measurement for FR1-FR1 NR-DC |
Nokia, Nokia Shanghai Bell |
| R4-2306326 |
Draft CR on HO with PSCell requirements for FR1-FR1 NR-DC |
Xiaomi |
| R4-2306327 |
draft CR for Rel-18 eFeRRM NR-DC FR1-FR1 SCG activation |
Ericsson |
| R4-2306328 |
Draft CR on scheduling availability of UE during intra-frequency measurements for FR1+FR1 NR-DC |
OPPO |
| 5.9.4 |
Moderator summary and conclusions |
|
| R4-2306152 |
Topic summary for [106-bis-e][204] NR_RRM_enh3_part1 |
Moderator (Apple) |
| R4-2306153 |
Topic summary for [106-bis-e][205] NR_RRM_enh3_part2 |
Moderator (OPPO) |
| R4-2306235 |
Topic summary for [106-bis-e][204] NR_RRM_enh3_part1 |
Moderator (Apple) |
| R4-2306236 |
Topic summary for [106-bis-e][205] NR_RRM_enh3_part2 |
Moderator (OPPO) |
| R4-2306315 |
WF on R18 RRM enhancement (part 1) |
Apple |
| R4-2306316 |
Topic summary for [106-bis-e][204] NR_RRM_enh3_part1 |
Moderator (Apple) |
| R4-2306321 |
LS on FR2 unknown SCell activation enhancement |
Apple |
| R4-2306322 |
WF on R18 RRM enhancement - FR1+FR1 NR-DC |
OPPO |
| R4-2306329 |
Draft Big CR for R18 RRM enhancement - FR1+FR1 NR-DC |
OPPO |
| 5.10.2.1 |
Scope and general issues |
|
| R4-2304074 |
Further consideration on scope and general issues for Pre-MG, concurrent MGs and NCSG |
vivo |
| R4-2304230 |
Discussion on using scenarios for pre-configured MGs, multiple concurrent MGs and NCSG |
Intel Corporation |
| R4-2304284 |
On R18 gap enhancement scope and general issues |
Apple |
| R4-2304990 |
Discussion on general and scope of enhancements on measurement gaps |
ZTE Corporation |
| R4-2305665 |
On joint requirements for Rel-17 measurement gap enhancements - scope and general issues |
Qualcomm Incorporated |
| R4-2305684 |
Discussion on general issues for Case 1 and Case 2 requirements |
Nokia, Nokia Shanghai Bell |
| 5.10.2.2 |
Case 1 requirements (Pre-configured MG and concurrent MG) |
|
| R4-2304075 |
Further consideration on case 1 requirements for Pre-MG and concurrent MGs |
vivo |
| R4-2304231 |
Discussion on RRM requirements for combinations of pre-configured MGs and multiple concurrent MGs |
Intel Corporation |
| R4-2304285 |
On R18 gap enhancement case 1 requirements |
Apple |
| R4-2304416 |
Discussion on case 1 requirements for combination of pre-MG and concurrent MGs |
CATT |
| R4-2304590 |
Discussion on case 1 requirements (Pre-configured MG and concurrent MG) |
MediaTek inc. |
| R4-2304763 |
RRM requirements for the combination of Pre-MG and concurrent MG |
Xiaomi |
| R4-2304837 |
Discussion on Pre-MG MG and concurrent MG (case 1) |
CMCC |
| R4-2304888 |
Discussion on PreMG and ConMGs |
Ericsson |
| R4-2304991 |
Discussion on Case 1 RRM requirements |
ZTE Corporation |
| R4-2305023 |
Discussion on Case 1 requirements for Pre-MG and concurrent MG |
China Telecom |
| R4-2305215 |
Discussion on case 1 requirements for Pre-MG and concurrent MG |
OPPO |
| R4-2305326 |
Discussion on joint working of pre-MG and con-MG |
Huawei, HiSilicon |
| R4-2305666 |
On joint requirements for Rel-17 measurement gap enhancements - Case 1 |
Qualcomm Incorporated |
| R4-2305685 |
Discussion on Case 1 requirements |
Nokia, Nokia Shanghai Bell |
| 5.10.2.3 |
Case 2 requirements (NCSG and concurrent MG) |
|
| R4-2304076 |
Further consideration on case 2 requirements for concurrent MGs and NCSG |
vivo |
| R4-2304232 |
Discussion on RRM requirements for combinations of NCSG and multiple concurrent MGs |
Intel Corporation |
| R4-2304286 |
On R18 gap enhancement case 2 requirements |
Apple |
| R4-2304417 |
Discussion on case 2 requirements for combination of NCSG and concurrent MGs |
CATT |
| R4-2304481 |
Discussion on RRM core requirement for case 2 (NCSG and concurrent MG) |
LG Electronics Finland |
| R4-2304591 |
Discussion on case 2 requirements (NCSG and concurrent MG) |
MediaTek inc. |
| R4-2304764 |
RRM requirements for the combination of NCSG and concurrent MG |
Xiaomi |
| R4-2304838 |
Discussion on NCSG and concurrent MG (case 2) |
CMCC |
| R4-2304889 |
Discussion on NCSG and ConMGs |
Ericsson |
| R4-2304992 |
Discussion on Case 2 RRM requirements |
ZTE Corporation |
| R4-2305024 |
Discussion on Case 2 requirements for NCSG and concurrent MG |
China Telecom |
| R4-2305216 |
Discussion on case 2 requirements NCSG and conMG |
OPPO |
| R4-2305327 |
Discussion on joint working of NCSG and con-MG |
Huawei, HiSilicon |
| R4-2305667 |
On joint requirements for Rel-17 measurement gap enhancements - Case 2 |
Qualcomm Incorporated |
| R4-2305686 |
Discussion on Case 2 requirements |
Nokia, Nokia Shanghai Bell |
| 5.10.3.1 |
Measurement without gaps for UEs reporting NeedForGapsInfoNR |
|
| R4-2304055 |
Discussion on measurements without gaps |
Nokia, Nokia Shanghai Bell |
| R4-2304077 |
Further considerations on Measurement without gaps for UEs reporting NeedForGapsInfoNR |
vivo |
| R4-2304233 |
Discussion on measurements without gaps when UE reporting NFG |
Intel Corporation |
| R4-2304287 |
On measurement without gaps for UEs reporting NeedForGapsInfoNR |
Apple |
| R4-2304288 |
LS on measurement without gaps for UEs reporting NeedForGapsInfoNR |
Apple |
| R4-2304382 |
Discussion on requirements for measurement without gaps for R18needforgap |
Qualcomm Incorporated |
| R4-2304418 |
Discussion on RRM requirements for measurement without gaps for UEs reporting NeedForGapsInfoNR |
CATT |
| R4-2304592 |
Discussion on measurement without gaps for UEs reporting NeedForGapsInfoNR |
MediaTek inc. |
| R4-2304775 |
Discussion on measurement without gaps for UEs reporting NeedForGapsInfoNR |
Xiaomi |
| R4-2304839 |
Discussion on measurements without gaps for UEs reporting NeedForGapsInfoNR |
CMCC |
| R4-2304890 |
Discussion on NeedForGaps measurement |
Ericsson |
| R4-2304993 |
Discussion on measurement without gaps for UEs reporting NeedForGapsInfoNR |
ZTE Corporation |
| R4-2305217 |
On measurement without gaps for UEs reporting NeedForGapsInfoNR |
OPPO |
| R4-2305328 |
Discussion on requirements for NeedForGaps |
Huawei, HiSilicon |
| 5.10.3.2 |
Inter-RAT measurement without gap |
|
| R4-2304078 |
Further considerations on Inter-RAT measurement without gap |
vivo |
| R4-2304214 |
Discussion on Inter-RAT measurements |
Nokia, Nokia Shanghai Bell |
| R4-2304234 |
Discussion on inter-RAT measurement without gaps |
Intel Corporation |
| R4-2304289 |
On R18 inter-RAT measurement without gap |
Apple |
| R4-2304383 |
Discussion on requirements of inter-RAT measurement without gaps. |
Qualcomm Incorporated |
| R4-2304419 |
Discussion on RRM requirements for Inter-RAT measurement without gap |
CATT |
| R4-2304593 |
Discussion on inter-RAT measurements |
MediaTek inc. |
| R4-2304776 |
Discussion on inter-RAT measurement without gap |
Xiaomi |
| R4-2304840 |
Discussion on inter-RAT measurements without gaps |
CMCC |
| R4-2304891 |
Discussion on Inter-RAT measurement without gap |
Ericsson |
| R4-2304994 |
Discussion on inter-RAT measurement without gaps |
ZTE Corporation |
| R4-2305218 |
On RRM requirements for Inter-RAT measurement without gap |
OPPO |
| R4-2305329 |
Discussion on inter-RAT MG-less measurement |
Huawei, HiSilicon |
| 5.10.4 |
Moderator summary and conclusions |
|
| R4-2306154 |
Topic summary for [106-bis-e][206] NR_MG_enh2_part1 |
Moderator (MediaTek) |
| R4-2306155 |
Topic summary for [106-bis-e][207] NR_MG_enh2_part2 |
Moderator (Intel) |
| R4-2306237 |
Topic summary for [106-bis-e][206] NR_MG_enh2_part1 |
Moderator (MediaTek) |
| R4-2306238 |
Topic summary for [106-bis-e][207] NR_MG_enh2_part2 |
Moderator (Intel) |
| R4-2306330 |
WF on Rel-18 NR MG enhancements (part 1) |
MediaTek |
| R4-2306331 |
WF on Rel-18 NR MG enhancements (part 2) |
Intel Corporation |
| R4-2306332 |
LS on interRAT measurements without gap |
Intel Corporation |
| 5.11.1 |
General and work plan |
|
| R4-2304043 |
Revised WID: Complete the specification support for BandWidth Part operation without restriction in NR |
Vodafone Italia SpA, vivo |
| R4-2304044 |
R18 workplan for Complete the specification support for BandWidth Part operation without restriction in NR NR WI |
Vodafone Italia SpA, vivo |
| R4-2306334 |
R18 workplan for Complete the specification support for BandWidth Part operation without restriction in NR NR WI |
Vodafone Italia SpA, vivo |
| 5.11.2 |
RRM core requirements |
|
| R4-2304252 |
Views on the solutions for bandwidth part operation without restriction |
Intel Corporation |
| R4-2304428 |
Discussion on the RRM impact of option A, B-1-1, B-1-2 and C for the support for bandwidth part operation without restriction |
CATT |
| 5.11.2.1 |
Impact of Option A |
|
| R4-2304303 |
On BWP w/o restriction - RRM core requirements for option A |
Apple |
| R4-2304594 |
Discussion on BWP operation without BW restrictions – Option A |
MediaTek inc. |
| R4-2304655 |
Discussion on impact of Option A |
CMCC |
| R4-2305045 |
On RRM impact of option A for BWP operation without restriction |
vivo |
| R4-2305341 |
Discussion on option A for BWP without restriction |
Huawei, HiSilicon |
| R4-2305554 |
Bandwidth part operation without restriction in NR – Option A |
Nokia, Nokia Shanghai Bell |
| R4-2305794 |
Analysis of BWP operation without restriction option A |
Ericsson |
| R4-2305809 |
Discussion on option A for BWP operation without restriction |
Spreadtrum Communications |
| 5.11.2.2 |
Impact of Option B-1-1 |
|
| R4-2304304 |
On BWP w/o restriction - RRM core requirements for option B-1-1 |
Apple |
| R4-2304595 |
Discussion on BWP operation without BW restrictions – Option B-1-1 |
MediaTek inc. |
| R4-2304656 |
Discussion on impact of Option B-1-1 |
CMCC |
| R4-2305047 |
On RRM impact of option B-1-1 for BWP operation without restriction |
vivo |
| R4-2305342 |
Discussion on option B-1-1 for BWP without restriction |
Huawei, HiSilicon |
| R4-2305555 |
Bandwidth part operation without restriction in NR – Option B-1-1 |
Nokia, Nokia Shanghai Bell |
| R4-2305795 |
Analysis of BWP operation without restriction option B-1-1 |
Ericsson |
| 5.11.2.3 |
Impact of Option C |
|
| R4-2304305 |
On BWP w/o restriction - RRM core requirements for option C |
Apple |
| R4-2304596 |
Discussion on BWP operation without BW restrictions – Option C |
MediaTek inc. |
| R4-2304657 |
Discussion on impact of Option C |
CMCC |
| R4-2305046 |
On RRM impact of option C for BWP operation without restriction |
vivo |
| R4-2305343 |
Discussion on option C for BWP without restriction |
Huawei, HiSilicon |
| R4-2305556 |
Bandwidth part operation without restriction in NR – Option C |
Nokia, Nokia Shanghai Bell |
| R4-2305796 |
Analysis of BWP operation without restriction option C |
Ericsson |
| 5.11.2.4 |
Impact of Option B-1-2 |
|
| R4-2304306 |
On BWP w/o restriction - RRM core requirements for option B-1-2 |
Apple |
| R4-2304597 |
Discussion on BWP operation without BW restrictions – Option B-1-2 |
MediaTek inc. |
| R4-2304658 |
Discussion on impact of Option B-1-2 |
CMCC |
| R4-2305048 |
On RRM impact of option B-1-2 for BWP operation without restriction |
vivo |
| R4-2305344 |
Discussion on option B-1-2 for BWP without restriction |
Huawei, HiSilicon |
| R4-2305557 |
Bandwidth part operation without restriction in NR – Option B-1-2 |
Nokia, Nokia Shanghai Bell |
| R4-2305797 |
Analysis of BWP operation without restriction option B-1-2 |
Ericsson |
| 5.11.3 |
Moderator summary and conclusions |
|
| R4-2306156 |
Topic summary for [106-bis-e][208] NR_BWP_wor |
Moderator (Vivo) |
| R4-2306239 |
Topic summary for [106-bis-e][208] NR_BWP_wor |
Moderator (Vivo) |
| R4-2306333 |
WF on BWP operation without restriction |
Vivo |
| R4-2306348 |
LS on L3 measurements for the options for BWP operation without restriction |
vivo, Vodafone Italia SpA |
| R4-2306393 |
Topic summary for [106-bis-e][208] NR_BWP_wor |
Moderator (Vivo) |
| 5.12.1 |
General and work plan |
|
| R4-2304307 |
LS on signaling support for intra-band non-collocated CA |
Apple |
| 5.12.2 |
UE RF architecture and RF requirements |
|
| R4-2304041 |
Discussion on viable UE architectures |
Nokia, Ericsson |
| R4-2304085 |
Discussion on non-collocated EN-DC,NR-CA |
KDDI Corporation, LG Uplus |
| R4-2304160 |
UE configuration assumptions for Type-2/3 |
SoftBank Corp. |
| R4-2304308 |
On type 3a/3b UE for intra-band non-collocated CA/EN-DC |
Apple |
| R4-2304694 |
Discussion on UE RF of non-collocated EN-DC and NR-CA |
ZTE Corporation |
| R4-2304719 |
Views on non-collocated deployment |
Samsung |
| R4-2304872 |
Discussion on intra-band non-co-located |
MediaTek Inc. |
| R4-2305099 |
Discussion on Type-3 UE RF requirement |
vivo |
| R4-2305530 |
Performance issues for Non-collocated Deployments |
Qualcomm Incorporated |
| R4-2305657 |
UE Architectures Suitable for Non-Collocated Intra-Band CA/EN-DC Rel18 |
Huawei Technologies France |
| 5.12.3 |
RRM Core requirements |
|
| R4-2304309 |
CR on scheduling Restriction for intra-band non-collocated CA type 2 UE |
Apple, Huawei |
| R4-2304698 |
Discussion on RRM requirements for non-collocated intra-band scenario |
Nokia, Nokia Shanghai Bell, Ericsson |
| R4-2304817 |
Discussion on RRM requirements for FR1 non-co-located EN-DC and NR-CA |
MediaTek inc. |
| R4-2304835 |
MRTD and MTTD for UE architecture Type 4 |
Ericsson, Nokia |
| R4-2304836 |
MRTD/MTTD requirement for non-collocated inter-band EN-DC with overlapping bands and intra band non-contiguous NR-CA. |
Ericsson, Nokia |
| R4-2305169 |
Discussion on RRM requirements for non-collocated EN-DC and NR-CA |
NTT DOCOMO, INC. |
| R4-2305200 |
Discussion on non-collocated FR1 inter-band EN-DC with overlapping DL bands and FR1 intra-band NR-CA deployment |
Samsung |
| R4-2305201 |
Draft CR to TS38.133 on MTTD/MRTD and interruption requirements for Rel-18 intra-band CA Type-2 UE |
Samsung |
| R4-2305317 |
Discussion on RRM requirements for supporting intra-band non-collocated EN-DC/NR-CA deployment |
Huawei, HiSilicon |
| R4-2305318 |
DraftCR on interruption requirements for supporting non-collocated FR1 intra-band CA |
Huawei, HiSilicon, Apple |
| R4-2306336 |
CR on scheduling Restriction for intra-band non-collocated CA type 2 UE |
Apple, Huawei |
| R4-2306337 |
Draft CR to TS38.133 on MTTD/MRTD and interruption requirements for Rel-18 intra-band CA Type-2 UE |
Samsung |
| R4-2306338 |
DraftCR on interruption requirements for supporting non-collocated FR1 intra-band CA |
Huawei, HiSilicon, Apple |
| 5.12.4 |
Demodulation performance requirements |
|
| R4-2304086 |
Work plan for demodulation performance part of WI intra-band non-colocated EN-DC/NR-CA deployment |
KDDI Corporation, Ericsson |
| R4-2304102 |
Demodulation requirements for non-collocated FR1 intra-band EN-DC/NR-CA |
Nokia, Nokia Shanghai Bell |
| R4-2304157 |
Dinamically Restricted PDSCH Scheduling for Intra-band Non-colocated NR CA Scenarios |
Apple |
| R4-2304693 |
Discussion on demodulation requirement for non-collocated Intra-Band EN-DC NR-CA and inter-band EN-DC |
ZTE Corporation |
| R4-2305181 |
UE demodulation requirements for non-colocated NR-CA/EN-DC deployment scenario |
Ericsson |
| R4-2305469 |
Discussions on demodulation requirements for non-collocated EN-DC/NR-CA deployment |
Huawei,HiSilicon |
| 5.12.5 |
Moderator summary and conclusions |
|
| R4-2305866 |
Topic Summary [106bis-e][320] NonCol_intraB_ENDC_NR_CA_Demod |
Moderator (Ericsson) |
| R4-2305891 |
WF on UE demodulation requirements for intra-band non-collocated EN-DC/NR-CA deployment scenario |
Ericsson |
| R4-2305989 |
Topic Summary [106bis-e][320] NonCol_intraB_ENDC_NR_CA_Demod |
Moderator (Ericsson) |
| R4-2306157 |
Topic summary for [106-bis-e][209] NonCol_intraB_ENDC_NR_CA |
Moderator (Huawei) |
| R4-2306210 |
Topic summary for [106-bis-e][131] NonCol_intraB |
Moderator (KDDI) |
| R4-2306240 |
Topic summary for [106-bis-e][209] NonCol_intraB_ENDC_NR_CA |
Moderator (Huawei) |
| R4-2306293 |
Topic summary for [106-bis-e][131] NonCol_intraB |
Moderator (KDDI) |
| R4-2306335 |
WF on RRM requirements for intra-band non-collocated EN-DC/NR-CA |
Huawei |
| R4-2306339 |
Draft Big CR on RRM requirements for support of intra-band non-collocated EN-DC/NR-CA deployment |
Huawei |
| R4-2306605 |
WF on UE RF requirements for intra-band non-collocated EN-DC/NR-CA deployment |
KDDI |
| 5.13.3 |
RF requirement for simultaneous multi-panel operation for train roof-mounted FR2 high power devices |
|
| R4-2304480 |
UE RF requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304631 |
On Multi-panel RF requirements for NR FR2 HST enhancement |
Huawei, HiSilicon |
| R4-2304831 |
Further discussion on feasibility and requirements for simultaneous multi-panel operation for FR2 HST |
Samsung |
| 5.13.4.1 |
Simultaneous multi-panel operation for train roof-mounted FR2 high power devices |
|
| R4-2304228 |
Simultaneous multi-panel operations for HST FR2 |
Intel Corporation |
| R4-2304271 |
On Simultaneous Multi-Panel Reception in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| R4-2305193 |
Multi-panel reception requirements for enhanced HST FR2 |
Ericsson |
| R4-2305213 |
Discussion on RRM impact by multi-panel simultaneous reception for FR2 HST UE |
Samsung |
| R4-2305284 |
Discussion on multi-panel simultaneous reception in FR2 eHST |
Huawei, HiSilicon |
| 5.13.4.2 |
Intra-band carrier aggregation (CA) scenario |
|
| R4-2304272 |
On RRM Impact by CA in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| R4-2304770 |
Discussion on RRM requirements for intra-band CA |
Xiaomi |
| R4-2305192 |
CA requirements for enhanced HST FR2 |
Ericsson |
| R4-2305285 |
Discussion on RRM requirements for intra-band CA in FR2 eHST |
Huawei, HiSilicon |
| R4-2305435 |
Discussion on Intra-band carrier aggregation (CA) scenario for FR2 HST |
Samsung |
| R4-2305804 |
Intra-band CA requirements for FR2 HST |
Qualcomm Incorporated |
| 5.13.4.3 |
UL timing adjustment solutions |
|
| R4-2304273 |
On UL Timing Adjustment in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| R4-2304772 |
Discussion on UL timing adjustment solutions for FR2 HST enhancement |
Xiaomi |
| R4-2305194 |
UL timing adjustment solutions |
Ericsson |
| R4-2305212 |
Discussion on UL timing adjustment solutions for FR2 HST |
Samsung |
| R4-2305319 |
Discussion on UL timing adjustment for R18 FR2 HST |
Huawei, HiSilicon |
| R4-2305805 |
UL timing adjustment solutions for FR2 HST |
Qualcomm Incorporated |
| 5.13.4.4 |
RRM aspects for tunnel deployment scenario |
|
| R4-2304274 |
On RRM Aspects of Tunnel Deployment Scenarios in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| R4-2304275 |
System Simulations Results for Tunnel Deployment Scenario in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| R4-2305190 |
LS on UE-initiate TCI state switch |
Ericsson |
| R4-2305191 |
RRM aspects for tunnel deployment scenario |
Ericsson |
| R4-2305211 |
Discussion on Tunnel deployment scenario |
Samsung |
| R4-2305803 |
RRM aspects for tunnel deployment scenario for FR2 HST |
Qualcomm Incorporated |
| 5.13.5.1 |
General and channel modelling |
|
| R4-2304259 |
General aspects on FR2 HST simultaneous multi-panel demodulation |
Intel Corporation |
| R4-2304276 |
On Channel Modelling in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| R4-2305484 |
Discussion on general issues about demodulation requirements for HST FR2 |
Huawei,HiSilicon |
| R4-2305541 |
View on channel modeling for Rel-18 FR2 HST demodulation requirement |
Samsung |
| R4-2305542 |
Updated work plan for performance part of Rel-18 FR2 HST |
Samsung |
| 5.13.5.2 |
UE demodulation requirements |
|
| R4-2304458 |
HST FR2 Enhanced UE Demodulation Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304493 |
Discussion on UE Demodulation requirements for FR2 HST Enh |
Qualcomm Incorporated |
| R4-2305182 |
UE demodulation requirements for FR2 HST enhancements |
Ericsson |
| R4-2305486 |
Discussion on UE demodulation requirements for HST FR2 |
Huawei,HiSilicon |
| R4-2305539 |
View on UE demodulation requirements for Rel-18 FR2 HST |
Samsung |
| 5.13.5.3 |
BS demodulation requirements |
|
| R4-2304277 |
HST FR2 Enhanced BS Demodulation Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2305183 |
BS demodulation requirements for FR2 HST enhancements |
Ericsson |
| R4-2305485 |
Discussion on BS demodulation requirements for HST FR2 |
Huawei,HiSilicon |
| R4-2305538 |
View on BS demodulation requirements for Rel-18 FR2 HST |
Samsung |
| 5.13.5.4 |
Demodulation aspects for tunnel deployment scenario |
|
| R4-2304260 |
FR2 HST tunnel deployment scenario and channel model |
Intel Corporation |
| R4-2304278 |
On Demodulation aspects of Tunnel Deployment Scenarios in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| R4-2305184 |
Tunnel deployment scenario for FR2 HST enhancements |
Ericsson |
| R4-2305483 |
Discussion on reference tunnel deployment scenario |
Huawei,HiSilicon |
| R4-2305540 |
View on demodulation requirements for tunnel deployment scenario for Rel-18 FR2 HST |
Samsung |
| 5.13.6 |
Moderator summary and conclusions |
|
| R4-2305867 |
Topic Summary [106bis-e][321] NR_HST_FR2_enh_Demod |
Moderator (Samsung) |
| R4-2305892 |
WF on demodulation requirements for Rel-18 FR2 HST |
Samsung |
| R4-2305893 |
Simulation assumption for PDSCH requirement with CA |
Ericsson |
| R4-2305990 |
Topic Summary [106bis-e][321] NR_HST_FR2_enh_Demod |
Moderator (Samsung) |
| R4-2306158 |
Topic summary for [106-bis-e][210] NR_HST_FR2_enh_part1 |
Moderator (Samsung) |
| R4-2306159 |
Topic summary for [106-bis-e][211] NR_HST_FR2_enh_part2 |
Moderator (Nokia) |
| R4-2306211 |
Topic summary for [106-bis-e][132] NR_HST_FR2_enh_UERF |
Moderator (Samsung) |
| R4-2306241 |
Topic summary for [106-bis-e][210] NR_HST_FR2_enh_part1 |
Moderator (Samsung) |
| R4-2306242 |
Topic summary for [106-bis-e][211] NR_HST_FR2_enh_part2 |
Moderator (Nokia) |
| R4-2306294 |
Topic summary for [106-bis-e][132] NR_HST_FR2_enh_UERF |
Moderator (Samsung) |
| R4-2306340 |
WF on simultaneous multi-panel operation for FR2 HST PC6 UE |
Samsung |
| R4-2306341 |
WF on intra-band CA for FR2 HST PC6 UE |
Ericsson |
| R4-2306342 |
WF on NR FR2 HST UL Timing Adjustment Solutions and Tunnel Deployment |
Nokia, Nokia Shanghai Bell |
| R4-2306343 |
LS on MAC-CE Based Indication for Cross-RRH TCI State Switch. |
Nokia, Nokia Shanghai Bell |
| R4-2306398 |
WF on NR FR2 HST UL Timing Adjustment Solutions and Tunnel Deployment |
Nokia, Nokia Shanghai Bell |
| R4-2306399 |
LS on MAC-CE Based Indication for Cross-RRH TCI State Switch |
Nokia, Nokia Shanghai Bell |
| R4-2306606 |
WF on NR FR2 HST UE RF |
Samsung |
| 5.14 |
Air-to-ground network for NR |
|
| R4-2304282 |
TR 38.876 v0.3.0 ATG |
CMCC |
| 5.14.1 |
FR1 co-existence evaluation for ATG network |
|
| R4-2304210 |
TP for TR 38.876 to add Annex |
CMCC |
| 5.14.1.2 |
Co-existence scenario and network layout |
|
| R4-2304205 |
discussion on ATG simulation assumption |
CMCC |
| R4-2304549 |
TP to TR 38.876: Update of assumptions for scenarios 2, 3, 10, 11 |
Ericsson |
| R4-2306608 |
TP to TR 38.876: Update of assumptions for scenarios 2, 3, 10, 11 |
Ericsson |
| 5.14.1.3 |
Co-existence system parameters and modeling |
|
| R4-2304203 |
ATG simulation results from CMCC |
CMCC |
| R4-2304547 |
Calibration results |
Ericsson |
| 5.14.1.4 |
Co-existence simulation results |
|
| R4-2304204 |
collection of ATG calibration results |
CMCC |
| R4-2304392 |
Preliminary ATG coexistence results |
Qualcomm CDMA Technologies |
| R4-2304442 |
ATG co-existence simulation results |
CATT |
| R4-2304548 |
Initial co-existence simulation results |
Ericsson |
| R4-2305372 |
Discussion on 2GHz and 4GHz simulation result for ATG scenario |
Huawei, HiSilicon |
| R4-2305397 |
The simulation results for ATG coexistence study |
ZTE Corporation |
| 5.14.2.1 |
General aspects |
|
| R4-2304315 |
TP for TR 38.876: General aspects |
Apple |
| R4-2306610 |
TP for TR 38.876: General aspects |
Apple |
| 5.14.2.2 |
Tx requirements |
|
| R4-2304206 |
Discussion on ATG UE Tx requirements |
CMCC |
| R4-2304316 |
TP for TR 38.876: Transmit signal quality |
Apple |
| R4-2304674 |
On ATG UE Tx reuqirements |
Qualcomm Incorporated |
| R4-2305005 |
Discussion on remaining ATG UE RF Tx requirements |
Ericsson |
| R4-2305373 |
Discussion on ATG UE Tx requirements |
Huawei, HiSilicon |
| R4-2305374 |
TP for TR 38.876 to introduce ATG UE Tx requirements |
Huawei, HiSilicon |
| R4-2305394 |
Further discussion on ATG UE Tx RF requirements |
ZTE Corporation |
| R4-2306611 |
TP for TR 38.876: Transmit signal quality |
Apple |
| R4-2306614 |
TP for TR 38.876 to introduce ATG UE Tx requirements |
Huawei, HiSilicon |
| 5.14.2.3 |
Rx requirements |
|
| R4-2304207 |
Discussion on ATG UE Rx requirements |
CMCC |
| R4-2304675 |
On Rx requirements for ATG UE RF |
Qualcomm Incorporated |
| R4-2304676 |
TP on TR 38.876 for ATG UE Rx reuqirements |
Qualcomm Incorporated |
| R4-2305006 |
Discussion on remaining ATG UE RF Rx requirements |
Ericsson |
| R4-2305007 |
TP to TR 38.876 on ATG UE Rx requirements |
Ericsson |
| R4-2305375 |
Discussion on ATG UE Rx requirements |
Huawei, HiSilicon |
| R4-2305395 |
Further discussion on ATG UE Rx RF requirements |
ZTE Corporation |
| R4-2306612 |
TP on TR 38.876 for ATG UE Rx reuqirements |
Qualcomm Incorporated |
| R4-2306613 |
TP to TR 38.876 on ATG UE Rx requirements |
Ericsson |
| 5.14.3 |
BS RF requirements |
|
| R4-2304208 |
Discussion on ATG BS RF requirements |
CMCC |
| R4-2304209 |
TP for TR 38.876 to introduce ATG BS Rx requirements |
CMCC |
| R4-2304216 |
TP for TR 38.876 on BS RF requirements |
Huawei, Hisilicon |
| R4-2304449 |
TP for TR 38.876, On ATG BS class and BS type in clause 7.2.1 |
CATT |
| R4-2304450 |
TP for TR 38.876, On transmitter spurious emissions in clause 7.2.2.4 and ttransmitter intermodulation in clause 7.2.2.5 |
CATT |
| R4-2304546 |
BS RF considerations for ATG |
Ericsson |
| R4-2305396 |
Further discussion on ATG BS RF requirements |
ZTE Corporation |
| R4-2305895 |
TP for TR 38.876 to introduce ATG BS Rx requirements |
CMCC |
| R4-2305896 |
TP for TR 38.876 on BS RF requirements |
Huawei, Hisilicon |
| R4-2305897 |
TP for TR 38.876, On ATG BS class and BS type in clause 7.2.1 |
CATT |
| R4-2305898 |
TP for TR 38.876, On transmitter spurious emissions in clause 7.2.2.4 and ttransmitter intermodulation in clause 7.2.2.5 |
CATT |
| 5.14.4.1 |
General aspects |
|
| R4-2304635 |
TP to TR 38.876 RRM requirements for ATG network |
CMCC |
| R4-2304636 |
Discussion on general RRM requirements for ATG |
CMCC |
| R4-2304905 |
Discussion on general RRM requirements in ATG networks |
LG Electronics UK |
| R4-2304983 |
Discussion on general aspects for air-to-ground network for NR |
ZTE Corporation |
| R4-2305271 |
Discussion on general aspects of RRM requirements for ATG |
Huawei, HiSilicon |
| R4-2305729 |
Discussions on general ATG RRM requirements |
Ericsson |
| R4-2306345 |
TP to TR 38.876 RRM requirements for ATG network |
CMCC |
| 5.14.4.2 |
Mobility requirements |
|
| R4-2304406 |
Discussion on mobility requirements for Rel-18 ATG |
CATT |
| R4-2304498 |
Discussion on ATG Mobility Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304637 |
Discussion on RRM mobility requirements for ATG |
CMCC |
| R4-2304906 |
Discussion on mobility requirements for ATG RRM |
LG Electronics UK |
| R4-2304985 |
Discussion on mobility requirements for air-to-ground network for NR |
ZTE Corporation |
| R4-2305287 |
Discussion on mobility requirements for ATG |
Huawei, HiSilicon |
| R4-2305728 |
Discussions on ATG mobility requirements |
Ericsson |
| R4-2305806 |
Mobility requirements for R18 ATG UEs |
Qualcomm Incorporated |
| 5.14.4.3 |
Timing adjustments |
|
| R4-2304407 |
Discussion on timing adjustments for Rel-18 ATG |
CATT |
| R4-2304499 |
Discussion on ATG Timing Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304638 |
Discussion on RRM timing requirements for ATG |
CMCC |
| R4-2304834 |
On timing requirements in ATG |
Ericsson |
| R4-2304908 |
Discussion on guard period in TDD cell for ATG operation |
LG Electronics UK |
| R4-2304986 |
Discussion on timing adjustment for air-to-ground network for NR |
ZTE Corporation |
| R4-2305320 |
Discussion on timing requirements for ATG RRM |
Huawei, HiSilicon |
| R4-2305807 |
Timing requirements for R18 ATG UEs |
Qualcomm Incorporated |
| 5.14.4.4 |
Signaling characteristics |
|
| R4-2304639 |
Discussion on RRM Signalling characteristics requirements for ATG |
CMCC |
| R4-2305730 |
Discussions on signaling characteristics for ATG |
Ericsson |
| 5.14.4.5 |
Measurement requirements |
|
| R4-2304408 |
Discussion on measurement requirements for Rel-18 ATG |
CATT |
| R4-2304500 |
Discussion on ATG Measurement Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304640 |
Discussion on RRM measurement requirements for ATG |
CMCC |
| R4-2304892 |
Discussion on measurement requirement in ATG |
Ericsson |
| R4-2304907 |
Discussion on measurement for ATG operation |
LG Electronics UK |
| R4-2304984 |
Discussion on measurement requirements for air-to-ground network for NR |
ZTE Corporation |
| R4-2305349 |
Discussion on measurement requirements for ATG |
Huawei, HiSilicon |
| 5.14.5.1 |
General aspects |
|
| R4-2304261 |
General aspects on ATG demodulation performance requirements |
Intel Corporation |
| R4-2304396 |
Discussion on general issue for ATG demodulation |
Ericsson |
| R4-2304494 |
Discussion on ATG UE Demodulation requirement - General |
Qualcomm Incorporated |
| R4-2304641 |
Discussion on general demodulation assumptions for ATG |
CMCC |
| R4-2304692 |
Discussion on ATG scenarios |
ZTE Corporation |
| R4-2305474 |
Discussion on general aspects for NR ATG demodulation requirements |
Huawei,HiSilicon |
| R4-2305534 |
View on deployment and channel model for Rel-18 ATG demodulation requirement |
Samsung |
| 5.14.5.2 |
UE demodulation performance and CSI requirements |
|
| R4-2304495 |
Discussion on ATG UE Demodulation requirement – UE Demod |
Qualcomm Incorporated |
| R4-2304642 |
Discussion on UE demodulation and CSI requirements for ATG scenario |
CMCC |
| R4-2304691 |
Discussion on ATG UE demodulation |
ZTE Corporation |
| R4-2305476 |
Discussion on NR UE ATG demodulation requirements |
Huawei,HiSilicon |
| R4-2305478 |
Simulation results on NR UE ATG demodulation requirements |
Huawei,HiSilicon |
| R4-2305661 |
On UE demodulation scope and PDSCH requirements for ATG network |
Ericsson |
| 5.14.5.3 |
BS demodulation performance requirements |
|
| R4-2304397 |
Discussion on ATG BS demodulation requirements |
Ericsson |
| R4-2304643 |
Discussion on BS demodulation requirements for ATG scenario |
CMCC |
| R4-2304668 |
Discussion on BS demodulation performance requirements |
ZTE Corporation |
| R4-2305475 |
Discussion on NR BS ATG demodulation requirements |
Huawei,HiSilicon |
| R4-2305477 |
Simulation results on NR BS ATG demodulation requirements |
Huawei,HiSilicon |
| R4-2305535 |
View on BS demodulation requirements for Rel-18 ATG |
Samsung |
| 5.14.6 |
Moderator summary and conclusions |
|
| R4-2305850 |
Topic Summary [106bis-e][303] NR_ATG_BSRF |
Moderator(Huawei) |
| R4-2305868 |
Topic Summary [106bis-e][322] NR_ATG_Demod |
Moderator (CMCC) |
| R4-2305894 |
WF for ATG BS RF requirements |
ZTE Corporation |
| R4-2305899 |
WF on ATG demodulation requirements |
CMCC |
| R4-2305973 |
Topic Summary [106bis-e][303] NR_ATG_BSRF |
Moderator(Huawei) |
| R4-2305991 |
Topic Summary [106bis-e][322] NR_ATG_Demod |
Moderator (CMCC) |
| R4-2306160 |
Topic summary for [106-bis-e][212] NR_ATG |
Moderator (CMCC) |
| R4-2306212 |
Topic summary for [106-bis-e][133] NR_ATG_UERF_part1 |
Moderator (CMCC) |
| R4-2306213 |
Topic summary for [106-bis-e][134] NR_ATG_UERF_part2 |
Moderator (Huawei) |
| R4-2306243 |
Topic summary for [106-bis-e][212] NR_ATG |
Moderator (CMCC) |
| R4-2306295 |
Topic summary for [106-bis-e][133] NR_ATG_UERF_part1 |
Moderator (CMCC) |
| R4-2306296 |
Topic summary for [106-bis-e][134] NR_ATG_UERF_part2 |
Moderator (Huawei) |
| R4-2306344 |
WF on NR ATG RRM core requirements |
CMCC |
| R4-2306607 |
WF on ATG co-existence simulation |
CMCC |
| R4-2306609 |
WF on ATG UE RF requirements |
Huawei, HiSilicon |
| 5.15.1 |
General and work plan |
|
| R4-2304122 |
Work split for BS RF CR drafting for NR support for dedicated spectrum less than 5MHz for FR1 |
Nokia, Nokia Shanghai Bell |
| 5.15.2 |
System parameters |
|
| R4-2304156 |
Cell search differentiation between legacy and sub-5MHz based on DMRS detection |
Apple |
| R4-2304269 |
Analysis of GB, Channel Size and Sync Raster for potential new 3MHz channel BW for NR FR1 less than 5MHz BW |
Intel Corporation |
| R4-2304571 |
Spectrum les than 5 MHz - System Parameters |
Ericsson |
| R4-2304875 |
Sync raster of NR support for dedicated spectrum less than 5MHz for FR1 |
Nokia, Nokia Shanghai Bell |
| R4-2305100 |
Discussion on system parameters of less than 5MHz |
vivo |
| R4-2305354 |
Discussion on system parameter for less than 5MHz NR channels |
ZTE Corporation |
| R4-2305504 |
LS out: System parameters for dedicated spectrum |
Qualcomm Inc. |
| R4-2305664 |
Synchronization raster for CBW of 3MHz |
Huawei Technologies France |
| R4-2305699 |
Further discussion on system parameters for sub-5MHz channel bandwidth |
MediaTek Inc. |
| 5.15.3 |
UE RF requirements |
|
| R4-2304042 |
draftCR to 38.101-1: Introduction of dedicated spectrum less than 5MHz for FR1 |
Nokia |
| R4-2304095 |
n26 A-MPR for 3 MHz channel |
Nokia, Nokia Shanghai Bell |
| R4-2304574 |
Spectrum les than 5 MHz - UE RF requirements |
Ericsson |
| R4-2304575 |
Draft CR to TS 38.101-1 - Introduction of 3 MHz channel bandwidth |
Ericsson |
| R4-2305361 |
draft CR to TS38.101-1 the introduction of 3 MHz channel bandwidth |
ZTE Corporation |
| R4-2305503 |
UE RF requirements for dedicated spectrum |
Qualcomm Inc. |
| R4-2305662 |
PC3 AMPR Evaluations for 3MHz CBW |
Huawei Technologies France |
| R4-2305700 |
Further discussion on UE RF requirements for sub-5MHz channel bandwidth |
MediaTek Inc. |
| 5.15.4 |
BS RF requirements |
|
| R4-2304123 |
BS RF specification impact for NR support for dedicated spectrum less than 5MHz for FR1 |
Nokia, Nokia Shanghai Bell |
| R4-2304572 |
Spectrum les than 5 MHz - BS RF requirements |
Ericsson |
| R4-2304573 |
Draft CR to TS 38.104 - Introduction of 3 MHz channel bandwidth |
Ericsson |
| R4-2305362 |
draft CR to TS38.104 the introduction of 3 MHz channel bandwidth |
ZTE Corporation |
| 5.15.5 |
RRM requirements |
|
| R4-2304151 |
RRM impacts overview for spectrum less than 5MHz |
Apple |
| R4-2304250 |
Discussion on RRM impact and features in FR1 less than 5 MHz BW |
Intel Corporation |
| R4-2304589 |
Discussion on Less than 5MHz RRM requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304599 |
Discussion on issues for less than 5MHz |
MediaTek inc. |
| R4-2305345 |
Discussion on RRM impacts for less than 5MHz BW |
Huawei, HiSilicon |
| R4-2305759 |
On RRM requirements for < 5MHz |
Ericsson |
| R4-2305772 |
On RRM requirements for < 5MHz |
Ericsson |
| R4-2305801 |
RRM requirements for NR less than 5MHz |
Qualcomm Incorporated |
| 5.15.6 |
Moderator summary and conclusions |
|
| R4-2305851 |
Topic Summary [106bis-e][304] NR_FR1_lessthan_5MHz_BW_BSRF |
Moderator (Nokia) |
| R4-2305900 |
WF on FRC parameters for link level simulation for added FRC |
ZTE Corporation |
| R4-2305901 |
WF on BS RF requirements |
Nokia |
| R4-2305902 |
LS on maximum BS output power for 3 MHz channel bandwidth in the paired frequency bands 874.4-880.0 MHz and 919.4-925.0 MHz for Railway Mobile Radio (RMR) |
UIC |
| R4-2305903 |
LS on receiver narrowband blocking for 3 MHz channel bandwidth in the paired frequency bands 874.4-880.0 MHz and 919.4-925.0 MHz for Railway Mobile Radio (RMR) |
Ericsson |
| R4-2305974 |
Topic Summary [106bis-e][304] NR_FR1_lessthan_5MHz_BW_BSRF |
Moderator (Nokia) |
| R4-2306161 |
Topic summary for [106-bis-e][213] NR_FR1_lessthan_5MHz_BW |
Moderator (Nokia) |
| R4-2306214 |
Topic summary for [106-bis-e][135] NR_FR1_lessthan_5MHz_BW |
Moderator (Nokia) |
| R4-2306244 |
Topic summary for [106-bis-e][213] NR_FR1_lessthan_5MHz_BW |
Moderator (Nokia) |
| R4-2306297 |
Topic summary for [106-bis-e][135] NR_FR1_lessthan_5MHz_BW |
Moderator (Nokia) |
| R4-2306346 |
WF on RRM requirements for NR FR1 less than 5MHz BW |
Nokia, Nokia Shanghai Bell |
| R4-2306347 |
WF on RRM simulation assumptions for NR FR1 less than 5MHz BW |
Nokia, Nokia Shanghai Bell |
| R4-2306400 |
WF on RRM simulation assumptions for NR FR1 less than 5MHz BW |
Nokia, Nokia Shanghai Bell |
| R4-2306615 |
WF on system requirements |
Nokia |
| R4-2306616 |
WF on UE RF requirements |
Nokia |
| 5.16.1 |
General and work plan |
|
| R4-2304034 |
Text proposal for Annex C on environment in TR 38.870 |
Huawei, HiSilicon, Samsung |
| R4-2304345 |
On device pool information for Rel-18 TRP TRS work |
Apple |
| R4-2305102 |
3GPP TR 38.870 v0.3.0 |
vivo |
| R4-2305106 |
Reply LS to GSMA TSGAP on NR Bandwidth for OTA TRS testing |
vivo |
| R4-2305531 |
TP to TR 38.870 on General parts |
CAICT,vivo |
| R4-2305610 |
Discussion on concept and definition of TRP |
OPPO |
| R4-2305785 |
TP on Test reductions with Measurement Grids |
Keysight Technologies UK Ltd |
| R4-2305905 |
Reply LS to GSMA TSGAP on NR Bandwidth for OTA TRS testing |
vivo |
| R4-2305908 |
TP to TR 38.870 on General parts |
CAICT,vivo |
| R4-2305909 |
TP on Test reductions with Measurement Grids |
Keysight Technologies UK Ltd |
| 5.16.2.1 |
Anechoic chamber test methodology |
|
| R4-2304028 |
on TRP TRS test aspects |
Huawei Tech.(UK) Co.. Ltd |
| R4-2304343 |
On TRP TRS test methodology |
Apple |
| R4-2304828 |
Discussion on TRP concept and test method for multi-antenna UE |
Samsung |
| R4-2305108 |
TP to TR 38.870 on forearm phantom |
vivo,CTIA Certification |
| R4-2305527 |
Further discussion on 2TX configuration |
Xiaomi |
| R4-2305532 |
TRP TRS test methodology |
CAICT |
| R4-2305607 |
Discussion on enhancement of test method for TRP and TRS |
Qualcomm Incorporated |
| R4-2305701 |
Further discussion on FR1 single layer UL-MIMO 2Tx SISO OTA TRP |
MediaTek Inc. vivo, CAICT |
| 5.16.2.2 |
Reverberation chamber test methodology |
|
| R4-2304027 |
Proposals for spatial uniformity and CBW test procedures in RC |
EMITE, BlueTest, Huawei, HiSilicon |
| R4-2304468 |
Discussion on Coherence bandwidth of RC |
EMITE, BlueTest, Huawei, HiSilicon |
| R4-2305004 |
On the minimum coherence bandwidth of RC |
EMITE, BlueTest, Huawei, HiSilicon |
| R4-2305103 |
Discussions on RC test method and Harmonization activity |
vivo |
| R4-2305906 |
Proposals for spatial uniformity and CBW test procedures in RC |
EMITE, BlueTest, Huawei, HiSilicon |
| 5.16.2.3 |
MU assessment |
|
| R4-2305104 |
MU for measurement grids |
vivo |
| 5.16.2.4 |
Testing time reduction |
|
| R4-2305105 |
Discussions on Measurement grids for spec 38.161 |
vivo |
| 5.16.3 |
Performance requirements |
|
| R4-2304344 |
On TRP TRS performance phase priorities |
Apple |
| R4-2305107 |
Updated working procedure for Rel-18 TRP TRS requirements |
vivo |
| R4-2305167 |
Device’s information disclosure for FR1 TRP-TRS and MIMO OTA |
TELECOM ITALIA S.p.A. |
| R4-2305186 |
Device’s information disclosure for FR1 TRP-TRS and MIMO OTA |
TELECOM ITALIA S.p.A. |
| R4-2305533 |
Discussion on FR1 TRP TRS requirements priority |
CAICT |
| R4-2305612 |
On disclosure of UE information |
OPPO |
| R4-2305615 |
On performance metric for UL-MIMO radiated power |
OPPO |
| R4-2305907 |
Updated working procedure for Rel-18 TRP TRS requirements |
vivo |
| 5.16.4 |
Moderator summary and conclusions |
|
| R4-2305875 |
Topic Summary [106bis-e][329] NR_FR1_TRP_TRS_enh |
Moderator (Vivo) |
| R4-2305904 |
WF on FR1 TRP TRS |
Vivo |
| R4-2305998 |
Topic Summary [106bis-e][329] NR_FR1_TRP_TRS_enh |
Moderator (Vivo) |
| 5.17.1 |
General and work plan |
|
| R4-2305123 |
Framework and time plan for FR1 MIMO OTA performance requirements development |
CAICT |
| R4-2305911 |
Framework and time plan for FR1 MIMO OTA performance requirements development |
CAICT |
| 5.17.2 |
FR2 MIMO OTA test methodology enhancement |
|
| R4-2304677 |
Views on FR2 MIMO OTA requirements |
Qualcomm Incorporated |
| R4-2304829 |
On EN-DC band combination selection for FR2 MIMO OTA |
Samsung |
| R4-2305498 |
Discussion on FR2 MIMO OTA test methodology enhancement |
Huawei,HiSilicon |
| R4-2305526 |
on the FR2 MIMO OTA |
Xiaomi |
| 5.17.3 |
FR1 MIMO OTA test methodology enhancement |
|
| R4-2304026 |
on MIMO OTA test with hand phantom |
Huawei Tech.(UK) Co.. Ltd |
| R4-2304073 |
Research on FR1 MIMO OTA noise impact at low band |
MediaTek Beijing Inc. |
| R4-2304215 |
Noise impact of FR1 low frequency for CMCC&BUPT joint lab |
CMCC |
| R4-2305122 |
Further views on FR1 MIMO OTA test for smartphone with hand phantom |
CAICT, SAICT |
| R4-2305363 |
Alternative method to accommodate single-panel UEs in FR2 MIMO OTA requirement |
Apple |
| R4-2305525 |
on the FR1 MIMO OTA |
Xiaomi |
| R4-2305613 |
On FR1 MIMO OTA in browsing mode |
OPPO |
| R4-2305784 |
On Phantom Testing and QZ Sizes |
Keysight Technologies UK Ltd |
| 5.17.4 |
MU assessment |
|
| R4-2305608 |
MU budget for FR2 MIMO OTA test system |
Qualcomm Incorporated |
| 5.17.5 |
Performance requirements |
|
| R4-2304346 |
On FR1 MIMO OTA lab alignment PADs roaming |
Apple |
| R4-2304347 |
On FR2 MIMO OTA lab alignment PADs roaming |
Apple, ETS-Lindgren |
| R4-2304830 |
Discussion on single panel UE in FR2 MIMO OTA campaign |
Samsung |
| R4-2305124 |
Views on FR2 MIMO OTA lab alignment |
CAICT |
| R4-2305614 |
On hybrid approach for FR2 MIMO OTA |
OPPO |
| 5.17.6 |
Moderator summary and conclusions |
|
| R4-2305876 |
Topic Summary [106bis-e][330] NR_MIMO_OTA_enh |
Moderator (CAICT) |
| R4-2305910 |
WF on Rel-18 MIMO OTA |
CAICT |
| R4-2305999 |
Topic Summary [106bis-e][330] NR_MIMO_OTA_enh |
Moderator (CAICT) |
| 5.18.2 |
BS EMC enhancements |
|
| R4-2304096 |
Discussion on BS EMC enhancements |
Nokia, Nokia Shanghai Bell |
| R4-2304681 |
Discussion on BS EMC test simplification |
ZTE Corporation |
| R4-2305187 |
BS EMC enhancement |
Ericsson |
| 5.18.3 |
UE EMC enhancements |
|
| R4-2305518 |
on UE EMC |
Xiaomi |
| 5.18.4 |
Moderator summary and conclusions |
|
| R4-2305852 |
Topic Summary [106bis-e][305] NR_LTE_EMC_enh |
Moderator (Ericsson) |
| R4-2305912 |
WF on BS EMC enhancements |
Ericsson |
| R4-2305913 |
WF on UE EMC enhancements |
Xiaomi |
| R4-2305975 |
Topic Summary [106bis-e][305] NR_LTE_EMC_enh |
Moderator (Ericsson) |
| 5.19.1 |
Advanced receiver to cancel inter-user interference for MU-MIMO |
|
| R4-2305119 |
Discussion on Advanced receiver to cancel inter-user interference for MU-MIMO |
MediaTek inc. |
| 5.19.1.1 |
Receiver assumption |
|
| R4-2304107 |
On Advanced Receivers - Receiver assumption |
Nokia, Nokia Shanghai Bell |
| R4-2304138 |
On advanced receiver to cancel intra-user interference for MU-MIMO |
Apple |
| R4-2304253 |
Views on the advanced MU-MIMO receiver assumptions |
Intel Corporation |
| R4-2304359 |
MU-MIMO discussion |
Qualcomm, Inc. |
| R4-2304669 |
Discussion on MU-MIMO receiver assumption |
ZTE Corporation |
| R4-2304684 |
Discussion on the receiver assumptions for the advanced receiver for MU-MIMO |
China Telecom |
| R4-2304902 |
discussion on MU-MIMO receiver assumption |
Samsung |
| R4-2305468 |
Discussions on advanced receiver for MU-MIMO |
Huawei,HiSilicon |
| R4-2305658 |
On the receiver assumption of intra-cell inter-user interference cancellation |
Ericsson |
| 5.19.1.2 |
Test parameters and simulation results |
|
| R4-2304108 |
On Advanced Receivers - Test parameters |
Nokia, Nokia Shanghai Bell |
| R4-2304109 |
Advanced Receivers - Simulation results |
Nokia, Nokia Shanghai Bell |
| R4-2304139 |
On test parameters and simulation results for MU-MIMO |
Apple |
| R4-2304254 |
Initial simulation results of advanced receivers for MU-MIMO |
Intel Corporation |
| R4-2304670 |
Discussion on MU-MIMO test parameters and simulation results |
ZTE Corporation |
| R4-2304685 |
Discussion on the phase I study assumptions for the advanced receiver for MU-MIMO |
China Telecom |
| R4-2304686 |
Phase I study for the advanced receiver for MU-MIMO: simulation results |
China Telecom |
| R4-2304687 |
Simulation result collection for advanced receiver for MU-MIMO |
China Telecom |
| R4-2305470 |
Simulation results on advanced receiver for MU-MIMO |
Huawei,HiSilicon |
| R4-2305659 |
On the left open issues and parameter assumptions for intra-cell inter-user interference cancellation |
Ericsson |
| R4-2305660 |
Simulation results for phase I study of intra-cell inter-user interference cancellation |
Ericsson |
| 5.19.2 |
Absolute physical layer throughput requirements with link adaptation |
|
| R4-2304110 |
On Absolute physical layer throughput requirements with link adaptation |
Nokia, Nokia Shanghai Bell |
| R4-2304111 |
Absolute physical layer throughput requirements - Simulation results |
Nokia, Nokia Shanghai Bell |
| R4-2304140 |
On Requirements for physical layer throughput |
Apple |
| R4-2304141 |
On Simulation Results for physical layer throughput |
Apple |
| R4-2304255 |
Views on the remaining issues for the specification of absolute physical layer throughput requirements |
Intel Corporation |
| R4-2304256 |
Simulation results of absolute physical layer throughput with link adaptation |
Intel Corporation |
| R4-2304257 |
Summary of simulation results for NR UE absolute physical layer throughput requirements with link adaptation |
Intel Corporation |
| R4-2304360 |
Application layer throughput discussion |
Qualcomm, Inc. |
| R4-2304644 |
Simulation results for ATP demodulation requirements |
CMCC |
| R4-2304645 |
Discussion for ATP demodulation requirements |
CMCC |
| R4-2304683 |
Discussion on absolute physical layer throughput requirements with link adaptation |
China Telecom |
| R4-2304903 |
discussion on absolute physical layer throughput with link adaptation |
Samsung |
| R4-2304904 |
simulation results on absolute physical layer throughput with link adaptation |
Samsung |
| R4-2305120 |
Discussion on Application Layer Data Throughput |
MediaTek inc. |
| R4-2305173 |
Simulation results of absolute physical layer throughput requirements |
Ericsson |
| R4-2305174 |
Open issues on absolute physical layer throughput requirements |
Ericsson |
| R4-2305467 |
Discussions on ATP requirements |
Huawei,HiSilicon |
| 5.19.3 |
Moderator summary and conclusions |
|
| R4-2305869 |
Topic Summary [106bis-e][323] NR_demod_enh3_Part1 |
Moderator (China Telecom) |
| R4-2305870 |
Topic Summary [106bis-e][324] NR_demod_enh3_Part2 |
Moderator (Intel) |
| R4-2305914 |
WF on advanced receiver for MU-MIMO scenario |
China Telecom |
| R4-2305915 |
WF on absolute physical layer throughput requirement |
Intel Corporation |
| R4-2305992 |
Topic Summary [106bis-e][323] NR_demod_enh3_Part1 |
Moderator (China Telecom) |
| R4-2305993 |
Topic Summary [106bis-e][324] NR_demod_enh3_Part2 |
Moderator (Intel) |
| 5.20.1 |
General and work plan |
|
| R4-2304036 |
Sub band full duplex simulations in RAN 4 and RAN 1 |
Spark NZ Ltd |
| R4-2304535 |
Clarifications on RAN1 LS Reply |
Nokia, Nokia Shanghai Bell |
| R4-2304542 |
On the LS response to RAN1 |
Ericsson |
| 5.20.2 |
Study the feasibility of and impact on RF requirements |
|
| R4-2304191 |
discussion on LS to RAN1 |
CMCC |
| R4-2304441 |
Draft reply LS on interference modelling for duplex evolution |
CATT |
| R4-2305074 |
Discussion and reply LS on interference modelling for duplex evolution |
vivo |
| R4-2305202 |
Discussion on interference modelling for duplex evolution and reply LS |
Samsung |
| R4-2305307 |
Discussion on reply LS on interference modelling |
Huawei, HiSilicon |
| 5.20.2.1 |
Adjacent channel co-existence evaluation |
|
| R4-2304060 |
Coexistence simulation results for SBFD |
Qualcomm CDMA Technologies |
| R4-2304092 |
TP to TR 38.858: Addition of simulation assumptions relevant for SBFD coexistence evaluation in Annex D |
Ericsson |
| R4-2304093 |
SBFD coexistence simulation results |
Ericsson |
| R4-2304190 |
study on SBFD co-existence simulation assumption |
CMCC |
| R4-2304195 |
SBFD simulation results from CMCC |
CMCC |
| R4-2304434 |
SBFD adjacent channel co-existence simulation results |
CATT |
| R4-2304536 |
Discussion on assumptions and simulation results for SBFD coexistence evaluation |
Nokia, Nokia Shanghai Bell |
| R4-2305248 |
Co-ex study calibration and results sharing for SBFD |
Samsung |
| R4-2305249 |
Adjacent channel co-ex study of SBFD |
Samsung |
| R4-2305250 |
Offline calibration data collection |
Samsung |
| R4-2305399 |
Initial Simulation results for full duplex coexistence in adjacent channel scenario |
ZTE Corporation |
| R4-2305558 |
On the co-existence study for NR duplex operation |
Huawei, HiSilicon |
| R4-2305924 |
Offline calibration data collection |
Samsung |
| 5.20.2.2.1 |
Feasibility of FR1 BS aspects |
|
| R4-2304192 |
study on feasibility at BS side |
CMCC |
| R4-2304267 |
Views on Interference Cancellation Feasibility in Sub-Band Full Duplex Operation for FR-1 Base Stations |
Intel Corporation |
| R4-2304431 |
TP for TR 38.858 Feasibility of FR1 Local Area BS aspects |
CATT |
| R4-2304433 |
Analysis on Local area BS feasibility for duplex evolution |
CATT |
| R4-2304540 |
Discussion on BS RF feasibility for FR1 with TP to TR 38.858 |
Nokia, Nokia Shanghai Bell |
| R4-2304543 |
TP to TR 38.858 section 10-1 Background for analysis |
Ericsson |
| R4-2304544 |
TP to TR 38.858 section 10.2 Feasibility of FR1 Wide Area BS aspects |
Ericsson |
| R4-2304882 |
TP to TR 38.858: feasibility of wide area BS aspects |
Qualcomm CDMA Technologies |
| R4-2304883 |
BS SBFD feasibility aspects |
Qualcomm CDMA Technologies |
| R4-2305203 |
Discussion on implementation feasibility study of SBFD: FR1 BS Aspects |
Samsung |
| R4-2305302 |
Discussion on the feasibility of FR1 BS aspects |
Huawei, HiSilicon |
| R4-2305400 |
Further discussion on full duplex from FR1 BS perspective |
ZTE Corporation |
| 5.20.2.2.2 |
Feasibility of FR2 BS aspects |
|
| R4-2304268 |
Views on Interference Cancellation Feasibility in Sub-Band Full Duplex Operation for FR-2 Base Stations |
Intel Corporation |
| R4-2304545 |
TP to TR 38.858 section 10.5 Feasibility of FR2 Wide Area BS aspects |
Ericsson |
| R4-2305204 |
Discussion on implementation feasibility study of SBFD: FR2 BS Aspects |
Samsung |
| R4-2305303 |
Discussion on the feasibility of FR2 BS aspects |
Huawei, HiSilicon |
| 5.20.2.2.3 |
Feasibility of FR1 UE aspects |
|
| R4-2304193 |
study on feasibility at FR1 UE side |
CMCC |
| R4-2304538 |
Considerations on feasibility of UE aspects |
Nokia, Nokia Shanghai Bell |
| R4-2305009 |
TP to TR 38.858 on Feasibility of FR1 UE aspects |
Ericsson |
| R4-2305075 |
TP on feasibility of FR1 UE aspects |
vivo |
| R4-2305205 |
Discussion on implementation feasibility study of SBFD: FR1 UE Aspects and TP to TR 38.858 |
Samsung |
| R4-2305304 |
Feasibility study from FR1 UE aspect |
Huawei, HiSilicon |
| R4-2305401 |
Discussion on SBFD capable FR1 UE RF requirement |
ZTE Corporation |
| R4-2305708 |
On feasibility of FR1 UE aspect |
MediaTek Inc. |
| R4-2305812 |
FR1 UE modelling |
Qualcomm Incorporated |
| R4-2305813 |
TP to TR 38.858 feasibility of and impact on FR1 UE RF requirements |
Qualcomm Incorporated |
| 5.20.2.2.4 |
Feasibility of FR2 UE aspects |
|
| R4-2304194 |
study on feasibility at FR2 UE side |
CMCC |
| R4-2305010 |
TP to TR 38.858 on Feasibility of FR2 UE aspects |
Ericsson |
| R4-2305076 |
TP on feasibility of FR2 UE aspects |
vivo |
| R4-2305206 |
Discussion on implementation feasibility study of SBFD: FR2 UE Aspects |
Samsung |
| R4-2305305 |
Feasibility study from FR2 UE aspect |
Huawei, HiSilicon |
| R4-2305709 |
On feasibility of FR2 UE aspect |
MediaTek Inc. |
| R4-2305811 |
FR2 UE modelling |
Qualcomm Incorporated |
| R4-2305814 |
TP to TR 38.858 feasibility of and impact on FR2 UE RF requirements |
Qualcomm Incorporated |
| R4-2305971 |
TP to TR 38.858 feasibility of and impact on FR2 UE RF requirements |
Qualcomm Incorporated |
| 5.20.2.3 |
Impacts on BS RF requirements |
|
| R4-2304400 |
SBFD feasibility study and RF impact on BS aspects |
Kumu Networks |
| R4-2304432 |
TP for TR 38.858 impact on BS RF requirements |
CATT |
| R4-2304537 |
Discussion on BS RF requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304541 |
SBFD BS feasibility considerations |
Ericsson |
| R4-2305306 |
BS RF requirement impact |
Huawei, HiSilicon |
| R4-2305402 |
Discussion on BS RF requirement impacts from SBFD perspective |
ZTE Corporation |
| 5.20.2.4 |
Impacts on UE RF requirements |
|
| R4-2305008 |
Discussion on remaining SBFD UE RF issues |
Ericsson |
| R4-2305077 |
Remaining issues for full duplex at UE side |
vivo |
| R4-2305710 |
Discussion on UE RF requirement impacts from SBFD |
MediaTek Inc. |
| 5.20.3 |
Summary of regulatory aspects |
|
| R4-2304024 |
Text Proposals for regulatory aspects in study on evolution of NR duplex operation |
Spark NZ Ltd |
| R4-2304539 |
TP to TR 38.858 Clause 13 regulatory aspects |
Nokia, Nokia Shanghai Bell |
| R4-2305207 |
Regulatory aspect of NR duplex evolution and TP to TR 38.858 |
Samsung |
| 5.20.4 |
Moderator summary and conclusions |
|
| R4-2305853 |
Topic Summary [106bis-e][306] FS_NR_duplex_evo_Part1 |
Moderator (Samsung) |
| R4-2305854 |
Topic Summary [106bis-e][307] FS_NR_duplex_evo_Part2 |
Moderator (Qualcomm) |
| R4-2305855 |
Topic Summary [106bis-e][308] FS_NR_duplex_evo_Part3 |
Moderator (CMCC) |
| R4-2305916 |
WF on implementation feasibility of SBFD: Self-interference |
Samsung |
| R4-2305917 |
WF on implementation feasibility of SBFD: Co-channel Co-site/inter-site interference |
Ericsson |
| R4-2305918 |
WF on BS RF requirement impact for SBFD |
CATT |
| R4-2305919 |
WF on regulatory aspects for SBFD |
CableLabs |
| R4-2305920 |
Reply LS on interference modelling for duplex evolution |
Samsung |
| R4-2305921 |
WF on SBFD co-existence simulation |
CMCC |
| R4-2305922 |
WF on Uma- Umi scenario simulation parameters |
CableLabs |
| R4-2305923 |
Summary of co-existence simulation parameters |
Samsung |
| R4-2305969 |
WF for SBFD feasibility study and requirements impact from UE aspect |
Qualcomm |
| R4-2305970 |
TP to TR 38.858 on Feasibility of FR1 UE aspects |
MediaTek |
| R4-2305976 |
Topic Summary [106bis-e][306] FS_NR_duplex_evo_Part1 |
Moderator (Samsung) |
| R4-2305977 |
Topic Summary [106bis-e][307] FS_NR_duplex_evo_Part2 |
Moderator (Qualcomm) |
| R4-2305978 |
Topic Summary [106bis-e][308] FS_NR_duplex_evo_Part3 |
Moderator (CMCC) |
| R4-2306004 |
Reply LS on interference modelling for duplex evolution |
Samsung |
| R4-2306005 |
WF on implementation feasibility of SBFD |
Samsung |
| R4-2306006 |
WF on implementation feasibility of SBFD |
Samsung |
| 5.21 |
Study on low-power wake-up signal and receiver for NR |
|
| R4-2305766 |
Views on low-power wake-up signal and receiver for NR |
Sony |
| 5.21.1 |
General and work plan |
|
| R4-2305112 |
[draft] reply LS to RAN1 on low-power wake-up receiver architectures |
vivo |
| R4-2305639 |
LS reply on low-power wake-up receiver architectures |
Ericsson |
| R4-2306618 |
reply LS to RAN1 on low-power wake-up receiver architectures |
vivo |
| 5.21.2 |
Evaluation of Low power wake-up receiver architectures |
|
| R4-2304103 |
RF aspects of low-power wake up receiver |
Nokia, Nokia Shanghai Bell |
| R4-2304196 |
discussion on low power WUS architectures |
CMCC |
| R4-2304283 |
Low-power wake-up receiver RF aspects |
Qualcomm Inc. |
| R4-2304342 |
On low-power wake-up signal and receiver for NR |
Apple |
| R4-2304722 |
Views on LP-WUR architectures |
Samsung |
| R4-2305110 |
Further discussions on low-power Wake-up Receiver architectures |
vivo |
| R4-2305126 |
Views on LP-WUR/LP-WUS |
ZTE Corporation |
| R4-2305567 |
Further consideration on LP-WUS/WUR |
Huawei, HiSilicon |
| R4-2305641 |
Evaluation of Low power wake-up receiver architectures |
Ericsson |
| R4-2305783 |
Further discussion on LP-WUR architecture |
MediaTek Inc. |
| 5.21.3 |
Evaluation of wake-up signal designs |
|
| R4-2304035 |
Evaluation of wake-up signal designs |
Nokia, Nokia Shanghai Bell |
| R4-2305111 |
Discussions on low-power Wake-up Signal designs |
vivo |
| R4-2305640 |
Evaluation of wake-up signal designs |
Ericsson |
| 5.21.4 |
Moderator summary and conclusions |
|
| R4-2306215 |
Topic summary for [106-bis-e][136] FS_NR_LPWUS |
Moderator (Vivo) |
| R4-2306298 |
Topic summary for [106-bis-e][136] FS_NR_LPWUS |
Moderator (Vivo) |
| R4-2306617 |
WF on LP-WUS |
Vivo |
| 5.22.1 |
General and work plan |
|
| R4-2304142 |
On RAN4 impact with introduction of AI/ML in air interface |
Apple |
| R4-2304167 |
Work plan for RAN4 discussions on AI/ML for NR air interface |
CAICT, ERICSSON, QUALCOMM |
| R4-2305158 |
Discussion on RAN4 works in Rel-18 AI/ML SI |
MediaTek inc. |
| R4-2305471 |
General Aspects and Work Plan for RAN4 R-18 SI on AI/ML for NR Air Interface |
Huawei,HiSilicon |
| R4-2305779 |
On terminologies for AI/ML |
Ericsson |
| 5.22.2 |
Specific issues related to use case for AI/ML |
|
| R4-2304126 |
On specific issues related to Use Cases for AI/ML in NR Air Interface |
Nokia, Nokia Shanghai Bell |
| R4-2304164 |
Discussion on use cases of AIML for NR air interface |
CAICT |
| R4-2304429 |
Discussion on specific issues related to use case for AI/ML |
CATT |
| R4-2304551 |
AI in PHY use case considerations for RAN4 |
Ericsson |
| R4-2304853 |
Discussion on use cases for AI/ML |
CMCC |
| R4-2305015 |
Discussion on RAN4 impact by use case for AI/ML |
Samsung |
| R4-2305050 |
Discussion on use cases for AI/ML |
vivo |
| R4-2305432 |
On specific issues related to use case for AIML |
OPPO |
| R4-2305472 |
Discussion on Specific Issues related to Use Case for AI/ML |
Huawei,HiSilicon |
| 5.22.3 |
Interoperability and testability aspect |
|
| R4-2304143 |
On testability with AI/ML in air interface |
Apple |
| R4-2304165 |
Discussion on Interoperability and testability aspect of AIML for NR air interface |
CAICT |
| R4-2304270 |
On Interoperability and Testability Aspects of AI/ML for NR Air Interface |
Nokia, Nokia Shanghai Bell |
| R4-2304361 |
AI/ML scope and general discussion |
Qualcomm, Inc. |
| R4-2304430 |
Discussion on interoperability and testability aspect for AI/ML |
CATT |
| R4-2304550 |
AI in PHY general considerations for RAN4 |
Ericsson |
| R4-2304854 |
Discussion on interoperability and testability for AI/ML |
CMCC |
| R4-2305000 |
Discussion on the Interoperability and testability aspects of AI&ML |
ZTE Corporation |
| R4-2305051 |
Discussion on Interoperability and testability aspects for AI/ML |
vivo |
| R4-2305199 |
Interoperability and testability aspect for AI/ML air interface |
Samsung |
| R4-2305251 |
On interoperability and testability for AIML |
Xiaomi |
| R4-2305433 |
On testability issues for two-sided AI/ML model |
OPPO |
| R4-2305473 |
Discussion on Interoperability and Testability Aspect |
Huawei,HiSilicon |
| 5.22.4 |
Moderator summary and conclusions |
|
| R4-2306216 |
Topic summary for [106-bis-e][137] FS_NR_AIML_air |
Moderator (Qualcomm) |
| R4-2306299 |
WF on AI/ML RAN4 studies |
Qualcomm |
| R4-2306619 |
Topic summary for [106-bis-e][137] FS_NR_AIML_air |
Moderator (Qualcomm) |
| 5.23.1 |
General and work plan |
|
| R4-2305687 |
General aspects for Rel-18 NR positioning |
Nokia, Nokia Shanghai Bell |
| 5.23.2 |
RF requirements |
|
| R4-2304440 |
Discussion on UE RF impact and the reply LS on switching time for RedCap UEs |
CATT |
| R4-2305035 |
LS to RAN2 on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs |
ZTE Corporation |
| R4-2305059 |
Draft Reply LS on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs |
vivo |
| R4-2305398 |
Discussion on RF requirements for bandwidth aggregated based positioning |
ZTE Corporation |
| R4-2305461 |
Reply LS to RAN 1 on switching time for DL PRS or UL SRS frequency hopping for RedCap Ues |
Huawei, HiSilicon |
| R4-2305645 |
LS reply for the switching time for RedCap UE positioning |
Ericsson |
| R4-2305676 |
Reply LS on switching time for DL PRS or UL SRS frequency hopping for RedCap Ues |
Qualcomm Incorporated |
| R4-2305680 |
NR positioning for RedCap UEs - switching time |
Intel Corporation |
| R4-2305693 |
UE RF requirements for Rel-18 NR positioning |
Nokia, Nokia Shanghai Bell |
| R4-2306476 |
LS reply for the switching time for RedCap UE positioning |
Ericsson |
| R4-2306659 |
LS reply for the switching time for RedCap UE positioning |
Ericsson |
| 5.23.3.1 |
General |
|
| R4-2305848 |
General RRM core requirements for Rel-18 Positioning |
Nokia, Nokia Shanghai Bell |
| 5.23.3.2 |
SL Positioning |
|
| R4-2304235 |
Discussion on Sidelink Positioning |
Intel Corporation |
| R4-2304420 |
Discussion on RRM requirements of sidelink positioning |
CATT |
| R4-2304482 |
Discussion on RRM core requirement for SL positioning enhancement |
LG Electronics Finland |
| R4-2304841 |
Discussion on sidelink positioning |
CMCC |
| R4-2305058 |
Discussion on RRM requirements for sidelink positioning |
vivo |
| R4-2305219 |
Discussion on SL positioning |
OPPO |
| R4-2305334 |
Discussion on RRM requirements for SL positioning |
Huawei, HiSilicon |
| R4-2305671 |
On requirements for SL positioning |
Qualcomm Incorporated |
| R4-2305688 |
Discussion on RRM requirements for SL positioning |
Nokia, Nokia Shanghai Bell |
| R4-2305771 |
On SL positioning |
Ericsson |
| 5.23.3.3 |
LPHAP use case |
|
| R4-2304236 |
Discussion on Positioning in LPHAP case 6 |
Intel Corporation |
| R4-2304421 |
Discussion on RRM requirements of LPHAP |
CATT |
| R4-2305028 |
Discussion on RRM aspects in the study on LPHAP use case |
ZTE Corporation |
| R4-2305220 |
Discussion on LPHAP use case |
OPPO |
| R4-2305335 |
Discussion on RRM requirements for LPHAP |
Huawei, HiSilicon |
| R4-2305570 |
RRM Core Requirements for LPHAP Use Case 6 in NR Positioning |
Nokia, Nokia Shanghai Bell |
| R4-2305674 |
On requirements for LPHAP |
Qualcomm Incorporated |
| R4-2305775 |
On LPHAP core requirements |
Ericsson |
| 5.23.3.4 |
RedCap Positioning |
|
| R4-2304237 |
Discussion on Positioning for RedCap UEs |
Intel Corporation |
| R4-2304422 |
Discussion on RRM requirements of Redcap positioning |
CATT |
| R4-2304624 |
Discussion on Positioning for RedCap UEs |
MediaTek inc. |
| R4-2305027 |
Discussion on RRM aspects in the study on Redcap positioning |
ZTE Corporation |
| R4-2305221 |
Discussion on RedCap positioning |
OPPO |
| R4-2305336 |
Discussion on RedCap positioning |
Huawei, HiSilicon |
| R4-2305337 |
Initial simulation results for PRS measurement with 1RX |
Huawei, HiSilicon |
| R4-2305571 |
RRM core requirements for RedCap positioning |
Nokia, Nokia Shanghai Bell |
| R4-2305672 |
Simulation results for 1Rx RedCap UEs without frequency hopping |
Qualcomm Incorporated |
| R4-2305673 |
On requirements for RedCap positioning |
Qualcomm Incorporated |
| R4-2305776 |
On RedCap positioning core requirements |
Ericsson |
| R4-2305777 |
Simulation results for 1Rx RedCap UE positioning measurements |
Ericsson |
| R4-2305778 |
Summary of simulation results for 1Rx RedCap UE positioning measurements |
Ericsson |
| 5.23.3.5 |
PRS/SRS bandwidth aggregation |
|
| R4-2304238 |
Discussion on Bandwidth Aggregation for Positioning |
Intel Corporation |
| R4-2304423 |
Discussion on RRM requirements of PRS/SRS bandwidth aggregation |
CATT |
| R4-2304483 |
Discussion on RRM core requirement for PRS/SRS bandwidth aggregation positioning |
LG Electronics Finland |
| R4-2305030 |
Discussion on RRM impacts on PRS/SRS bandwidth aggregation |
ZTE Corporation |
| R4-2305338 |
Discussion on PRS/SRS Bandwidth Aggregation |
Huawei, HiSilicon |
| R4-2305572 |
RRM Core Requirements for PRS/SRS Bandwidth Aggregation in NR Positioning |
Nokia, Nokia Shanghai Bell |
| R4-2305675 |
On requirements for PRS/SRS BW aggregation |
Qualcomm Incorporated |
| R4-2305773 |
On PRS/SRS aggregation core requirements |
Ericsson |
| 5.23.3.6 |
Carrier Phase Positioning |
|
| R4-2304239 |
Discussion on Carrier Phase Positioning |
Intel Corporation |
| R4-2304424 |
Discussion on RRM requirements of carrier phase positioning |
CATT |
| R4-2304484 |
Discussion on RRM core requirement for carrier phase positioning |
LG Electronics Finland |
| R4-2305029 |
Discussion on RRM aspects in the study on carrier phase positioning |
ZTE Corporation |
| R4-2305222 |
Discussion on carrier phase positioning |
OPPO |
| R4-2305339 |
Discussion on RRM requirements for CPP |
Huawei, HiSilicon |
| R4-2305689 |
RRM core requirements for NR Carrier Phase Positioning |
Nokia, Nokia Shanghai Bell |
| R4-2305774 |
On carrier phase positioning core requirements |
Ericsson |
| 5.23.4 |
Moderator summary and conclusions |
|
| R4-2306162 |
Topic summary for [106-bis-e][214] NR_pos_enh2_part1 |
Moderator (Ericsson) |
| R4-2306163 |
Topic summary for [106-bis-e][215] NR_pos_enh2_part2 |
Moderator (CATT) |
| R4-2306164 |
Topic summary for [106-bis-e][216] NR_pos_enh2_part3 |
Moderator Huawei) |
| R4-2306217 |
Topic summary for [106-bis-e][138] NR_pos_enh2_UERF |
Moderator (Intel) |
| R4-2306245 |
Topic summary for [106-bis-e][214] NR_pos_enh2_part1 |
Moderator (Ericsson) |
| R4-2306246 |
Topic summary for [106-bis-e][215] NR_pos_enh2_part2 |
Moderator (CATT) |
| R4-2306247 |
Topic summary for [106-bis-e][216] NR_pos_enh2_part3 |
Moderator Huawei) |
| R4-2306300 |
Topic summary for [106-bis-e][138] NR_pos_enh2_UERF |
Moderator (Intel) |
| R4-2306349 |
WF on RRM requirements for RedCap positioning and PRS/SRS BW aggregation |
Ericsson |
| R4-2306350 |
Updated simulation assumptions for 1Rx RedCap UE PRS measurements |
Ericsson |
| R4-2306351 |
WF on RRM requirements for NR sidelink positioning and carrier phase positioning |
CATT |
| R4-2306352 |
LS on the scenarios of carrier phase positioning |
CATT |
| R4-2306353 |
WF on RRM requirements for LPHAP |
Huawei, HiSilicon |
| R4-2306620 |
WF on UE RF aspects for Rel-18 NR positioning |
Intel Corporation |
| 5.24.1 |
General and work plan |
|
| R4-2304339 |
On UL MIMO and Tx switching capabilities |
Apple |
| 5.24.2.1 |
UL Tx switching with single TAG |
|
| R4-2304162 |
Simultaneous switching |
Qualcomm Incorporated |
| R4-2304338 |
On switching period in dualUL cases |
Apple |
| R4-2304340 |
Rel-18 band configurations and fallbacks for TX Switching across 3 or 4 bands |
Apple |
| R4-2304401 |
Remaining issues for NR Multi-carrier enhancements |
China Telecom |
| R4-2304402 |
CR for 38.101-1: Time mask for switching across three or four uplink bands |
China Telecom, [NTT DOCOMO, Huawei, Hisilicon, CMCC, OPPO, ZTE] |
| R4-2304465 |
On the time masks for 3-4 band switching, location of T_0 and support of fallbacks |
Ericsson |
| R4-2304873 |
Discussion on remaining issues on Tx switching |
MediaTek Inc. |
| R4-2304874 |
Draft LS on Rel-18 UL Tx switching |
MediaTek Inc. |
| R4-2305088 |
Further discussion on RF aspects of UL Tx switching with single TAG |
vivo |
| R4-2305129 |
On Tx switching across 3 or 4 bands for single TAG |
ZTE Corporation |
| R4-2305185 |
Views on Rel-18 Tx switching |
NTT DOCOMO INC. |
| R4-2305252 |
Discussion on UL Tx switching |
Xiaomi |
| R4-2305447 |
Discussion on Multi-carrier enhancements with single TAG |
Huawei, HiSilicon |
| R4-2305789 |
3 and 4 band TX switching open issues and requirements |
Qualcomm Incorporated |
| R4-2305808 |
draft CR on TX Switching when UE is configured for 3 or 4 bands UL |
Qualcomm Incorporated |
| 5.24.2.2 |
UL Tx switching with multiple TAGs |
|
| R4-2304466 |
Time masks for Tx switching with dual TAG |
Ericsson |
| R4-2305448 |
Discussion on Multi-carrier enhancements with multiple TAG |
Huawei, HiSilicon |
| R4-2305449 |
draftCR for 38.101-1 to clarify the time mask for switching with multiple TAGs |
Huawei, HiSilicon |
| 5.24.3.1 |
DL interruption for Tx switching across 3/4 bands |
|
| R4-2304124 |
DL interruption for Tx switching across 3/4 bands |
Nokia, Nokia Shanghai Bell |
| R4-2304125 |
DL interruption for Tx switching across 3/4 bands |
Nokia, Nokia Shanghai Bell |
| R4-2304170 |
DL interruption for Tx switching across 3/4 bands |
ZTE Corporation |
| R4-2304290 |
On DL interruption for Tx switching across 3/4 bands |
Apple |
| R4-2304358 |
Multi-carrier enhancement RRM |
Qualcomm, Inc. |
| R4-2304623 |
Discussion on DL interruption for Tx switching across 3&4 bands |
MediaTek inc. |
| R4-2305049 |
Remaining issues on DL interruption for Tx switching across 3 to 4 bands |
vivo |
| R4-2305282 |
Discussion on DL interruption for multi-carrier enhancements |
Huawei, HiSilicon |
| R4-2305283 |
DL interruption for Tx switching across 3/4 bands |
Huawei, HiSilicon |
| 5.24.4 |
Moderator summary and conclusions |
|
| R4-2306165 |
Topic summary for [106-bis-e][217] NR_MC_enh |
Moderator (Huawei) |
| R4-2306218 |
Topic summary for [106-bis-e][139] NR_MC_enh_UERF |
Moderator (China Telecom) |
| R4-2306248 |
Topic summary for [106-bis-e][217] NR_MC_enh |
Moderator (Huawei) |
| R4-2306301 |
Topic summary for [106-bis-e][139] NR_MC_enh_UERF |
Moderator (China Telecom) |
| R4-2306354 |
WF on RRM requirements for MC enhancements for NR |
Huawei, HiSilicon |
| R4-2306621 |
WF on Rel-18 Tx switching across 3/4 bands |
China Telecom |
| R4-2306622 |
WF on ambiguity issue when two Tx chains are switched between different band pairs |
MediaTek |
| R4-2306623 |
LS on Rel-18 Tx switching across 3/4 bands |
China Telecom |
| R4-2306660 |
WF on Tx switching ambiguity issue |
MediaTek Inc. |
| 5.25.2 |
L1/L2 based inter-cell mobility |
|
| R4-2304173 |
Reply LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM |
ZTE Corporation |
| 5.25.2.1 |
General aspects and scenarios |
|
| R4-2304171 |
Discussion on general aspects and scenarios of L1/L2 triggered inter-cell mobility |
ZTE Corporation |
| R4-2304223 |
Discussion on general aspects and scenarios of L1/L2 based inter-cell mobility |
China Telecom |
| R4-2304291 |
On L1/L2 based inter-cell mobility - General aspects and scenarios |
Apple |
| R4-2304365 |
Scenario and scope of RRM requirements for LTM |
Qualcomm Korea |
| R4-2304409 |
Discussion on general aspects and scenarios for L1/L2 based inter-cell mobility |
CATT |
| R4-2304583 |
Discussion on LTM General aspects and scenarios |
Nokia, Nokia Shanghai Bell |
| R4-2304765 |
Discussion on general aspects and scenarios for LTM |
Xiaomi |
| R4-2304809 |
Discussion on general aspects in R18 L1L2-triggered mobility |
vivo |
| R4-2304845 |
Discussion on general aspects for L1/L2 based inter-cell mobility |
CMCC |
| R4-2304923 |
Discussion on general aspects and scenarios of LTM |
MediaTek Inc. |
| R4-2305198 |
General aspects discussions for L1/L2 based inter-cell mobility |
NTT DOCOMO, INC. |
| R4-2305239 |
On general and scenarios of L1L2 based inter-cell mobility |
OPPO |
| R4-2305275 |
Discussion on general aspects on L1/L2 based inter-cell mobility |
Huawei, HiSilicon |
| R4-2305760 |
On LTM general aspects and scenarios |
Ericsson |
| 5.25.2.2 |
L1-RSRP measurement requirements |
|
| R4-2304224 |
Discussion on L1-RSRP measurement requirements of L1/L2 based inter-cell mobility |
China Telecom |
| R4-2304226 |
L1-RSRP measurement requirements for LTM operations |
Intel Corporation |
| R4-2304292 |
On L1/L2 based inter-cell mobility - L1-RSRP measurement requirements |
Apple |
| R4-2304366 |
L1-RSRP measurement requirements |
Qualcomm Korea |
| R4-2304410 |
Discussion on L1-RSRP measurement requirements for L1/L2 based inter-cell mobility |
CATT |
| R4-2304584 |
Discussion on LTM measurement requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304672 |
Discussion on L1-RSRP measurement requirements |
ZTE Corporation |
| R4-2304766 |
Discussion on L1-RSRP measurement requirements for LTM |
Xiaomi |
| R4-2304810 |
Discussion on L1 measurements in R18 L1L2-triggered mobility |
vivo |
| R4-2304847 |
Discussion on L1-RSRP measurement requirements for L1/L2 based inter-cell mobility |
CMCC |
| R4-2304924 |
Discussion on L1-RSRP measurement requirements for LTM |
MediaTek Inc. |
| R4-2305240 |
On L1-RSRP measurement of L1L2 based inter-cell mobility |
OPPO |
| R4-2305276 |
Discussion on L1-RSRP measurement requirements |
Huawei, HiSilicon |
| R4-2305761 |
On L1-RSRP measurement requirements |
Ericsson |
| 5.25.2.3 |
L1/L2 inter-cell mobility delay requirements |
|
| R4-2304225 |
Discussion on L1/L2 inter-cell mobility delay requirements |
China Telecom |
| R4-2304227 |
L1/L2 inter-cell mobility delay requirements |
Intel Corporation |
| R4-2304293 |
On L1/L2 based inter-cell mobility delay requirements |
Apple |
| R4-2304367 |
LTM handover delay requirements |
Qualcomm Korea |
| R4-2304411 |
Discussion on L1/L2 inter-cell mobility delay requirements |
CATT |
| R4-2304585 |
Discussion on LTM delay requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304673 |
Discussion on L1/L2 inter-cell mobility delay requirements |
ZTE Corporation |
| R4-2304767 |
Discussion on L1/L2 based inter-cell mobility delay requirement |
Xiaomi |
| R4-2304811 |
Discussion on cell switch delay requirements in R18 L1L2-triggered mobility |
vivo |
| R4-2304844 |
Discussion on L1/L2 inter-cell mobility delay requirements |
CMCC |
| R4-2304925 |
Discussion on LTM delay requirements |
MediaTek Inc. |
| R4-2305241 |
On L1L2 inter-cell mobility delay requirements |
OPPO |
| R4-2305277 |
Discussion on L1/L2 inter-cell mobility delay requirements |
Huawei, HiSilicon |
| R4-2305762 |
On LTM delay requirements |
Ericsson |
| 5.25.2.4 |
Others |
|
| R4-2304172 |
Discussion on LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM |
ZTE Corporation |
| R4-2304812 |
LS to RAN2 on the measurement framework in R18 LTM |
vivo |
| R4-2305278 |
Discussion on SFN alignment for L1/L2-based inter-cell mobility |
Huawei, HiSilicon |
| R4-2305763 |
Discussion on pre-sync aspects of LTM |
Ericsson |
| 5.25.3 |
NR-DC with selective activation of cell groups via L3 enhancements |
|
| R4-2304175 |
Discussion on NR-DC with selective activation of cell groups via L3 enhancment |
ZTE Corporation |
| R4-2304294 |
On NR-DC with selective activation of cell groups via L3 enhancements |
Apple |
| R4-2304384 |
Discussion on the requirement of subsequent CPC |
Qualcomm Incorporated |
| R4-2304412 |
Discussion on NR-DC with selective activation of cell groups via L3 enhancements |
CATT |
| R4-2304586 |
Discussion on NR-DC with selective activation of cell groups via L3 enhancements |
Nokia, Nokia Shanghai Bell |
| R4-2304848 |
Discussion on NR-DC with selective activation of cell groups via L3 enhancements |
CMCC |
| R4-2304894 |
Discussion on selective activaiton of the cell groups in NR-DC |
Ericsson |
| R4-2304926 |
Discussion on NR-DC with selective activation of cell groups via L3 enhancements |
MediaTek Inc. |
| R4-2305052 |
Discussion on NR-DC with selective activation of cell groups via L3 enhancements |
vivo |
| R4-2305242 |
On NR-DC with selective activation of cell groups via L3 enhancements |
OPPO |
| R4-2305279 |
NR-DC with selective activation of cell groups via L3 enhancements |
Huawei, HiSilicon |
| 5.25.4 |
Improvement on SCell/SCG setup delay |
|
| R4-2304174 |
Discussion on the improvement on SCell/SCG setup/resume |
ZTE Corporation |
| R4-2304249 |
Discussion on improvement on SCell/SCG setup delay |
Intel Corporation |
| R4-2304295 |
On improvement on FR2 SCell/SCG setup delay |
Apple |
| R4-2304385 |
Discussion on improvement on Scell/SCG setup delay |
Qualcomm Incorporated |
| R4-2304587 |
Discussion on Improvement on SCell/SCG setup delay |
Nokia, Nokia Shanghai Bell |
| R4-2304768 |
Discussion on improvement on SCell/SCG setup delay |
Xiaomi |
| R4-2304846 |
Discussion on improvement on SCell/SCG setup delay |
CMCC |
| R4-2304895 |
Disucssion on enhancement of FR2 Idle/Inactive measurement reporting |
Ericsson |
| R4-2304909 |
Discussion on improvement on SCell/SCG setup delay |
LG Electronics UK |
| R4-2304927 |
Discussion on improvement on SCell/SCG setup/resume |
MediaTek Inc. |
| R4-2305054 |
Discussion on RRM requirements of FR2 measurements for DC/CA setup/resume |
vivo |
| R4-2305243 |
On improvement on FR2 SCellSCG setupresume |
OPPO |
| R4-2305280 |
Discussion on improvement on FR2 SCell/SCG setup/resume |
Huawei, HiSilicon |
| 5.25.5 |
Enhanced CHO configurations |
|
| R4-2304176 |
Discussion on Enhanced CHO configurations |
ZTE Corporation |
| R4-2304296 |
On Enhanced CHO configurations |
Apple |
| R4-2304386 |
Discussion on Enhanced CHO configurations. |
Qualcomm Incorporated |
| R4-2304413 |
Discussion on enhanced CHO configurations |
CATT |
| R4-2304588 |
Discussion on Enhanced CHO configurations |
Nokia, Nokia Shanghai Bell |
| R4-2304896 |
Discussion on enhanced CHO configurations |
Ericsson |
| R4-2304928 |
Discussion on Enhanced CHO configurations |
MediaTek Inc. |
| R4-2305053 |
Discussion on Enhanced CHO configurations |
vivo |
| R4-2305244 |
On enhanced CHO configurations |
OPPO |
| R4-2305281 |
Discussion on Enhanced CHO configurations |
Huawei, HiSilicon |
| 5.25.6 |
Moderator summary and conclusions |
|
| R4-2306166 |
Topic summary for [106-bis-e][218] NR_Mob_enh2_part1 |
Moderator (MediaTek) |
| R4-2306167 |
Topic summary for [106-bis-e][219] NR_Mob_enh2_part2 |
Moderator (Apple) |
| R4-2306249 |
Topic summary for [106-bis-e][218] NR_Mob_enh2_part1 |
Moderator (MediaTek) |
| R4-2306250 |
Topic summary for [106-bis-e][219] NR_Mob_enh2_part2 |
Moderator (Apple) |
| R4-2306355 |
WF on NR Mobility Enhancements RRM requirements (part 1) |
MediaTek |
| R4-2306356 |
WF on NR Mobility Enhancements RRM requirements (part 2) |
Apple |
| R4-2306395 |
WF on NR Mobility Enhancements RRM requirements (part 1) |
MediaTek |
| R4-2306396 |
WF on NR Mobility Enhancements RRM requirements (part 2) |
Apple |
| 5.26.2 |
RRM requirements for Rel-17 MUSIM gaps |
|
| R4-2304516 |
LS on priority for MUSIM gaps |
vivo |
| 5.26.2.1 |
General aspects |
|
| R4-2304079 |
Further considerations on general aspects for MUSIM gaps |
vivo |
| R4-2304297 |
On R18 MUSIM - General aspects |
Apple |
| R4-2304616 |
Discussion on the general aspects of MUSIM gaps |
MediaTek inc. |
| R4-2304777 |
Discussion on general issues for Rel-17 MUSIM gaps |
Xiaomi |
| R4-2304852 |
Discussion on open issues for MUSIM gaps |
CMCC |
| R4-2304884 |
Discussions on general issues in MUSIM gaps |
Ericsson |
| R4-2305223 |
Discussion on general RRM requirements for Rel-17 MUSIM gaps |
OPPO |
| R4-2305333 |
Discussion on general issues related to MUSIM gaps |
Huawei, HiSilicon |
| R4-2305550 |
Discussion on General aspects |
Nokia, Nokia Shanghai Bell |
| 5.26.2.2 |
Collisions between gaps and priority rules |
|
| R4-2304080 |
Further considerations on collisions between gaps and priority rules for MUSIM gaps |
vivo |
| R4-2304298 |
On R18 MUSIM - collisions between gaps and priority rules |
Apple |
| R4-2304617 |
Discussion on RRM requirements for MUSIM gaps collision handling |
MediaTek inc. |
| R4-2304778 |
Discussion on collisions between gaps and priority rules for Rel-17 MUSIM gaps |
Xiaomi |
| R4-2304849 |
Discussion on collisions between gaps and priority rules for MUSIM gaps |
CMCC |
| R4-2304885 |
Discussions on collision between MUSIM gaps |
Ericsson |
| R4-2305032 |
Discussion on collisions between gaps and priority rules |
ZTE Corporation |
| R4-2305224 |
Discussion on collision between gap and priority rules |
OPPO |
| R4-2305330 |
Discussion on collision handling for MUSIM gaps |
Huawei, HiSilicon |
| R4-2305551 |
Collisions between gaps and priority rules |
Nokia, Nokia Shanghai Bell |
| R4-2305668 |
On requirements for Rel-17 MUSIM gaps - Gap collisions |
Qualcomm Incorporated |
| R4-2305697 |
Discussion on collisions between gaps and priority rules of MUSIM |
Charter Communications, Inc |
| 5.26.2.3 |
On network A requirements |
|
| R4-2304081 |
Further considerations on network A requirements for RRM requirements of MUSIM gaps |
vivo |
| R4-2304299 |
On R18 MUSIM - network A requirements |
Apple |
| R4-2304618 |
Discussion on NW A RRM requirements for MUSIM |
MediaTek inc. |
| R4-2304779 |
Discussion on network A requirements for Rel-17 MUSIM gaps |
Xiaomi |
| R4-2304850 |
Discussion on network A requirements for MUSIM gaps |
CMCC |
| R4-2304886 |
Discussions on NW-A’s requirement in MUSIM gaps |
Ericsson |
| R4-2305033 |
Discussion on Network A requirements |
ZTE Corporation |
| R4-2305225 |
Discussion on network A requirements |
OPPO |
| R4-2305331 |
Discussion on NW-A requirements with MUSIM gaps |
Huawei, HiSilicon |
| R4-2305552 |
On network A requirements |
Nokia, Nokia Shanghai Bell |
| R4-2305669 |
On requirements for Rel-17 MUSIM gaps - Network A requirements |
Qualcomm Incorporated |
| 5.26.2.4 |
On network B requirements |
|
| R4-2304082 |
Further considerations on network B requirements for RRM requirements of MUSIM gaps |
vivo |
| R4-2304300 |
On R18 MUSIM - network B requirements |
Apple |
| R4-2304619 |
Discussion on NW B RRM requirements for MUSIM |
MediaTek inc. |
| R4-2304780 |
Discussion on network B requirements for Rel-17 MUSIM gaps |
Xiaomi |
| R4-2304851 |
Discussion on network B requirements for MUSIM gaps |
CMCC |
| R4-2304887 |
Discussions on NW-B’s requirement in MUSIM gaps |
Ericsson |
| R4-2305034 |
Discussion on Network B requirements |
ZTE Corporation |
| R4-2305332 |
Discussion on NW-B requirements with MUSIM gaps |
Huawei, HiSilicon |
| R4-2305553 |
On network B requirements |
Nokia, Nokia Shanghai Bell |
| R4-2305670 |
On requirements for Rel-17 MUSIM gaps - Network B requirements |
Qualcomm Incorporated |
| 5.26.3 |
Moderator summary and conclusions |
|
| R4-2306168 |
Topic summary for [106-bis-e][220] NR_DualTxRx_MUSIM |
Moderator (Vivo) |
| R4-2306251 |
Topic summary for [106-bis-e][220] NR_DualTxRx_MUSIM |
Moderator (Vivo) |
| R4-2306357 |
WF on NR Dual TxRx Multi-SIM |
Vivo |
| 5.27.1.1 |
System parameters |
|
| R4-2304439 |
Further discussion on NTN system parameters |
CATT |
| R4-2304567 |
NTN enhancement: System parameters |
Ericsson |
| R4-2304938 |
Discussion on above 10GHz NTN bands |
Nokia, Nokia Shanghai Bell |
| R4-2305417 |
Further discussion on system parameter for NTN in Ka band |
ZTE Corporation |
| R4-2305831 |
Discussion on system parameters for above 10 GHz |
THALES |
| 5.27.1.2 |
Regulatory information |
|
| R4-2304566 |
NTN enhancement: Regulatory aspects |
Ericsson |
| 5.27.1.3 |
Others |
|
| R4-2305832 |
Discussion on RAN LS to RAN1 for NTN above 10 GHz |
THALES |
| 5.27.2 |
Co-existence study for above 10GHz bands |
|
| R4-2304363 |
Frequency ranges of GSO and NGSO ESIMs and coexistence requirements |
Verizon Denmark |
| R4-2304364 |
Off-Axis EIRP requirement |
Verizon Denmark |
| R4-2304443 |
Further discussion on remaining issues about simulation assumptions for above 10GHz NTN co-existence study |
CATT |
| R4-2304568 |
NTN enhancement: coexistence simulations |
Ericsson |
| R4-2304614 |
Simulation assumptions and preliminary co-existence study for above 10GHz NTN co-existence study |
Samsung Electronics Nordic AB |
| R4-2304615 |
Simulation assumptions and preliminary co-existence study for above 10GHz NTN co-existence study |
Samsung Electronics Nordic AB |
| R4-2304680 |
Simulation assumptions for co-existence study for above 10GHz bands |
Qualcomm Incorporated |
| R4-2305383 |
Discussion on Rel-18 NTN coexistence study assumption |
Huawei, HiSilicon |
| R4-2305834 |
NTN Simulation Parameters for above 10 GHz Coexistence Studies |
THALES, Magister Solutions Ltd |
| R4-2305847 |
Updated NTN Simulation Parameters for above 10 GHz Coexistence Studies and Initial Simulation Results |
THALES, Magister Solutions Ltd |
| 5.27.3 |
SAN RF requirements |
|
| R4-2304444 |
Further discussion on SAN RF requirements for above 10GHz bands |
CATT |
| R4-2304569 |
NTN enhancement: SAN RF requirements |
Ericsson |
| R4-2305418 |
Further discussion on SAN RF requirements for NTN in Ka-band |
ZTE Corporation |
| 5.27.4 |
UE RF requirements |
|
| R4-2304570 |
NTN enhancement: NTN UE requirements |
Ericsson |
| R4-2305065 |
On Beam Tracking Capabilities for measurements |
Nokia, Nokia Shanghai Bell |
| R4-2305384 |
Discussion on Ka band NTN UE |
Huawei, HiSilicon |
| R4-2305419 |
Further discussion on UE RF requirements for NTN in Ka-band |
ZTE Corporation |
| R4-2305844 |
NTN UE terminal reference architecture for above 10 GHz |
THALES, Hughes/EchoStar |
| 5.27.5 |
RRM core requirements |
|
| R4-2304154 |
RRM impacts overview for eNTN |
Apple |
| R4-2304368 |
NTN support for frequency band above 10GHz |
Qualcomm Korea |
| R4-2304425 |
Discussion on RRM requirements for NTN enhancement |
CATT |
| R4-2304501 |
Discussion on applicability of SCS for NTN above 10 GHz |
Nokia, Nokia Shanghai Bell |
| R4-2304646 |
Discussion on RRM core requirements for NR NTN enhancement |
CMCC |
| R4-2304745 |
Discussion on RRM impacts on NTN enhancement |
Samsung |
| R4-2304769 |
Discussion on RRM requirements for Rel-18 NTN |
Xiaomi |
| R4-2304818 |
Discussion on RRM requirements for NTN enhancement |
MediaTek inc. |
| R4-2304911 |
General views on NR NTN enhancement |
LG Electronics UK |
| R4-2305031 |
Discussion on RRM requirements for NTN enhancement |
ZTE Corporation |
| R4-2305055 |
Discussion on RRM requirements for NTN enhancement |
vivo |
| R4-2305195 |
RRM requirements for NR NTN enhancement |
Ericsson |
| R4-2305340 |
Discussion on RRM requirements for Rel-18 NTN |
Huawei, HiSilicon |
| R4-2305845 |
Discussion on RAN LS to RAN1 for NTN above 10 GHz |
THALES |
| 5.27.6 |
Moderator summary and conclusions |
|
| R4-2305856 |
Topic Summary [106bis-e][309] NR_NTN_enh_Part1 |
Moderator (Thales) |
| R4-2305857 |
Topic Summary [106bis-e][310] NR_NTN_enh_Part2 |
Moderator (Ericsson) |
| R4-2305858 |
Topic Summary [106bis-e][311] NR_NTN_enh_Part3 |
Moderator (Samsung) |
| R4-2305925 |
WF on NTN enhancement - [106bis-e][309] NR_NTN_enh_Part1 |
Thales |
| R4-2305926 |
LS on System Parameters for NTN above 10 GHz |
CATT |
| R4-2305927 |
WF on SAN RF requirements |
Ericsson |
| R4-2305928 |
WF on [311] NR_NTN_enh_Part3 |
Samsung |
| R4-2305929 |
Calibration table for NTN co-existence study in above 10GHz band |
Samsung |
| R4-2305930 |
Assumptions for NTN co-existence study in above 10GHz band |
Samsung |
| R4-2305979 |
Topic Summary [106bis-e][309] NR_NTN_enh_Part1 |
Moderator (Thales) |
| R4-2305980 |
Topic Summary [106bis-e][310] NR_NTN_enh_Part2 |
Moderator (Ericsson) |
| R4-2305981 |
Topic Summary [106bis-e][311] NR_NTN_enh_Part3 |
Moderator (Samsung) |
| R4-2306002 |
WF on [311] NR_NTN_enh_Part3 |
Samsung |
| R4-2306003 |
Assumptions for NTN co-existence study in above 10GHz band |
Samsung |
| R4-2306169 |
Topic summary for [106-bis-e][221] NR_NTN_enh |
Moderator (Qualcomm) |
| R4-2306219 |
Topic summary for [106-bis-e][140] NR_NTN_enh_UERF |
Moderator (ZTE) |
| R4-2306252 |
Topic summary for [106-bis-e][221] NR_NTN_enh |
Moderator (Qualcomm) |
| R4-2306302 |
Topic summary for [106-bis-e][140] NR_NTN_enh_UERF |
Moderator (ZTE) |
| R4-2306358 |
WF on NR NTN enhancement RRM requirements |
Qualcomm Incorporated |
| R4-2306359 |
LS on NR-NTN deployment in above 10 GHz |
Nokia |
| R4-2306624 |
WF on NTN UE RF requirements in Ka-band |
ZTE Corporation |
| 5.28.1 |
Enhancement of increasing UE power high limit for CA and DC |
|
| R4-2304087 |
PC and associated information reporting |
Nokia, Nokia Shanghai Bell |
| R4-2304146 |
Power-class fallback reporting in the PHR, the P-MPR method and the high-power limit |
Ericsson |
| R4-2304189 |
Discussion on the potential solutions for the enhancement for SAR issue |
Fujitsu Limited |
| R4-2304605 |
Draft LS on UE signaling to enhance UL reliability |
Qualcomm Incorporated |
| R4-2305092 |
Discussion of enhancement of increasing UE power high limit for CA and DC |
vivo |
| R4-2305137 |
General way to enable increase higher power limit feature for new CA and ENDC band combinations |
ZTE Corporation |
| R4-2305138 |
Draft CR to TS38.101-1_General way to enable increase higher power limit feature for new CA band combinations |
ZTE Corporation, CHTTL, samsung |
| R4-2305139 |
draft CR to TS38.101-3_General way to enable increase higher power limit feature for new ENDC band combinations |
ZTE Corporation, CHTTL, samsung |
| R4-2305172 |
Draft LS on Enhancement of increasing UE power high limit for CA and DC |
NTT DOCOMO INC. |
| R4-2305350 |
Discussion on enhancement of increasing UE maximum power high limit |
Xiaomi |
| R4-2305601 |
On enhancements of increasing UE power high limit for CA and DC |
Huawei, HiSilicon |
| 5.28.2 |
Enhancement to reduce MPR/PAR |
|
| R4-2304604 |
On link-level benefits of transparent and non-transparent PAPR reduction techniques |
Qualcomm Incorporated |
| R4-2305602 |
On further enhancements to reduce MPR/PAR |
Huawei, HiSilicon |
| R4-2305635 |
Background and way forward to use RAN1 LS with results on MPR/PAR reduction |
Ericsson |
| 5.28.2.1 |
General and work plan for Enhancement to reduce MPR/PAR |
|
| R4-2304933 |
Scope of the work for MPR/PAR -objective |
Nokia, Nokia Shanghai Bell |
| 5.28.2.2 |
RF simulation parameters |
|
| R4-2304934 |
RF simulation parameters for MPR/PAR evaluations |
Nokia, Nokia Shanghai Bell |
| R4-2305638 |
Simulation results for the transparent scheme |
Ericsson |
| 5.28.2.3 |
RF simulation results for transparent schemes |
|
| R4-2304935 |
RF simulation results for transparent schemes |
Nokia, Nokia Shanghai Bell |
| R4-2305116 |
RF simulation results for transparent schemes for enhancement to reduce MPR |
vivo |
| R4-2305636 |
simulation parameter discussion for transparent and non-transparent schemes |
Ericsson |
| 5.28.2.4 |
RF simulation results for non-transparent schemes |
|
| R4-2304318 |
Simulation results for non-transparent MPR reduction schemes |
Apple |
| R4-2304936 |
RF simulation results for non-transparent schemes |
Nokia, Nokia Shanghai Bell |
| R4-2305117 |
RF simulation results for non-transparent schemes for enhancement to reduce MPR |
vivo |
| R4-2305637 |
Simulation results for the non-transparent scheme |
Ericsson |
| 5.28.2.5 |
RF specification impact |
|
| R4-2304937 |
RF specification impacts |
Nokia, Nokia Shanghai Bell |
| R4-2305634 |
RF spec impact for MPR reduction scheme |
Ericsson |
| 5.28.3 |
Moderator summary and conclusions |
|
| R4-2306220 |
Topic summary for [106-bis-e][141] NR_cov_enh2_part1 |
Moderator (Huawei) |
| R4-2306221 |
Topic summary for [106-bis-e][142] NR_cov_enh2_part2 |
Moderator (Nokia) |
| R4-2306303 |
Topic summary for [106-bis-e][141] NR_cov_enh2_part1 |
Moderator (Huawei) |
| R4-2306304 |
Topic summary for [106-bis-e][142] NR_cov_enh2_part2 |
Moderator (Nokia) |
| R4-2306625 |
WF on NR further coverage enhancement part1 |
Huawei, HiSilicon |
| R4-2306626 |
LS on enhancements to realize increasing UE power high limit for CA and DC |
NTT DOCOMO, INC. |
| R4-2306627 |
WF on remaining open issues for MPR/PAR reduction for coverage enhancement |
Nokia |
| R4-2306628 |
WF on simulation results and observations for MPR/PAR reduction for coverage enhancement |
Huawei, HiSilicon |
| 5.29.1.1 |
System parameters |
|
| R4-2304199 |
discussion on NCR system parameter |
CMCC |
| R4-2304437 |
Discussion on NCR system parameters |
CATT |
| R4-2304530 |
Further discussions on NCR system parameters |
Nokia, Nokia Shanghai Bell |
| R4-2305170 |
Discussion on NCR class declaration on NCR type 1-H and 1-O |
NTT DOCOMO, INC. |
| R4-2305410 |
Discussion on system parameter for NCR-MT |
ZTE Corporation |
| 5.29.1.2 |
Others |
|
| R4-2304438 |
Discussion on NCR-MT feature list |
CATT |
| R4-2304709 |
Discussion on NCR types |
NEC |
| R4-2305411 |
Discussion on RAN4 feature list for NCR-MT |
ZTE Corporation |
| 5.29.2 |
RF core requirements |
|
| R4-2305412 |
Discussion on RF diagram for NCR |
ZTE Corporation |
| 5.29.2.1 |
RF requirements for NCR-Fwd |
|
| R4-2304201 |
discussion on NCR forwarding requirements |
CMCC |
| R4-2304445 |
Further discussion on RF requirements for NCR-Fwd |
CATT |
| R4-2304532 |
Discussion on NCR RF core requirements for NCR-fwd |
Nokia, Nokia Shanghai Bell |
| R4-2304552 |
Network controlled repeater RF parameters FWD |
Ericsson |
| R4-2305171 |
Discussion on NCR-Fwd Rx spurious emission |
NTT DOCOMO, INC. |
| R4-2305413 |
Discussion on RF requirements for NCR-Fwd |
ZTE Corporation |
| 5.29.2.2 |
RF requirements for NCR-MT |
|
| R4-2304200 |
discussion on NCR MT requirements |
CMCC |
| R4-2304446 |
Further discussion on RF requirements for NCR-MT |
CATT |
| R4-2304531 |
Reference sensitivity requirement for FR2 NCR-MT |
Nokia, Nokia Shanghai Bell |
| R4-2304554 |
Network controlled repeater RF parameters MT |
Ericsson |
| R4-2304710 |
Discussion on NCR power control |
NEC |
| R4-2305414 |
Discussion on RF requirements for NCR-MT |
ZTE Corporation |
| 5.29.3 |
EMC core requirements |
|
| R4-2304529 |
Discussion on NCR EMC core requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304682 |
Discussion on Network-Controlled Repeater EMC requirement |
ZTE Corporation |
| R4-2305188 |
EMC of NCR |
Ericsson |
| 5.29.4 |
RF conformance testing |
|
| R4-2304447 |
Discussion on RF conformance testing for NCR |
CATT |
| R4-2304533 |
NCR conformance testing |
Nokia, Nokia Shanghai Bell |
| R4-2304553 |
Network controlled repeater conformance |
Ericsson |
| R4-2305415 |
Discussion on conformance testing requirement for NCR |
ZTE Corporation |
| 5.29.5 |
RRM core requirements |
|
| R4-2304279 |
On NCR RRM Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304414 |
Discussion on RRM core requirements for NR Network-controlled Repeaters |
CATT |
| R4-2305321 |
Discussion on RRM requirements for NR network-controlled repeaters |
Huawei, HiSilicon |
| R4-2305416 |
Further discussion on RRM requirements for NCR-MT |
ZTE Corporation |
| R4-2305739 |
Further Discussion for NCR RRM requirements |
Dell Technologies |
| R4-2305790 |
Further analysis of RRM requirements for network controlled repeater |
Ericsson |
| 5.29.6 |
Demodulation performance requirements |
|
| R4-2304459 |
On NCR Demodulation Performance Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2304555 |
Network controlled repeater demodulation requirements |
Ericsson |
| R4-2304671 |
Discussion on demodulation performance requirements for NCR-MT |
ZTE Corporation |
| R4-2305487 |
Discussion on demodulation performance requirements for NR network-controlled repeaters |
Huawei,HiSilicon |
| 5.29.7 |
Moderator summary and conclusions |
|
| R4-2305859 |
Topic Summary [106bis-e][312] NR_netcon_repeater_RF |
Moderator (ZTE) |
| R4-2305860 |
Topic Summary [106bis-e][313] NR_netcon_repeater_RFConformance |
Moderator (CATT) |
| R4-2305871 |
Topic Summary [106bis-e][325] NR_netcon_repeater_Demod |
Moderator (ZTE) |
| R4-2305931 |
WF on system parameters and RF requirements |
ZTE Corporation |
| R4-2305932 |
WF on NCR EMC requirements |
ZTE Corporation |
| R4-2305933 |
WF on NR NCR RF conformance testing |
CATT |
| R4-2305934 |
WF on NCR-MT demodulation requirements |
ZTE Corporation |
| R4-2305982 |
Topic Summary [106bis-e][312] NR_netcon_repeater_RF |
Moderator (ZTE) |
| R4-2305983 |
Topic Summary [106bis-e][313] NR_netcon_repeater_RFConformance |
Moderator (CATT) |
| R4-2305994 |
Topic Summary [106bis-e][325] NR_netcon_repeater_Demod |
Moderator (ZTE) |
| R4-2306170 |
Topic summary for [106-bis-e][222] NR_netcon_repeater |
Moderator (ZTE} |
| R4-2306253 |
Topic summary for [106-bis-e][222] NR_netcon_repeater |
Moderator (ZTE} |
| R4-2306360 |
WF on RRM requirements for NR network controlled repeater |
ZTE |
| 5.30.2 |
UE RF requirements |
|
| R4-2305600 |
On the RF requirement for STxMP |
Huawei, HiSilicon |
| 5.30.2.1 |
Simultaneous transmission with multi-panel (STxMP) |
|
| R4-2304059 |
On UE RF requirements for STxMP mDCI case |
InterDigital Communications |
| R4-2304128 |
Power limit for STxMP |
Apple |
| R4-2304478 |
UE power limitation for STxMP in FR2 (R1-2205639) |
Nokia, Nokia Shanghai Bell |
| R4-2304600 |
On configured Tx power for STxMP in FR2 |
Qualcomm Incorporated |
| R4-2305014 |
Discussion on RF requirements of STxMP |
Samsung |
| R4-2305087 |
Discussion of UE RF requirements for STxMP in FR2 |
vivo |
| R4-2305836 |
Discussion on UE RF requirements for STxMP |
Ericsson Limited |
| R4-2306657 |
Reply LS on configured Tx power for STxMP in FR2 |
Qualcomm Incorporated |
| 5.30.2.2 |
Other UE RF impacts |
|
| R4-2304479 |
UE RF requirement aspects |
Nokia, Nokia Shanghai Bell |
| 5.30.3.1 |
RRM requirements impacts |
|
| R4-2304056 |
Discussion on MIMO evolution RRM impacts |
Nokia, Nokia Shanghai Bell |
| R4-2304144 |
On RRM requirements impacts for NR MIMO evolution for downlink and uplink |
Apple |
| R4-2304247 |
Discussion on FeMIMO SRS antenna port switching RRM impacts |
Intel Corporation |
| R4-2304742 |
Further discussion on general RRM impacts on Rel-18 MIMO evolution for downlink and uplink |
Samsung |
| R4-2304813 |
Discussion on other RRM impacts in R18 NR MIMO evolution WI |
vivo |
| R4-2304920 |
Discussion on R18 MIMO for RRM requirements impacts |
MediaTek Inc. |
| R4-2305322 |
Discussion on RRM impacts for R18 MIMO evolution |
Huawei, HiSilicon |
| R4-2305528 |
Reply LS on RAN4 RRM agreements for Rel-18 MIMO |
Samsung |
| R4-2305764 |
On RRM requirements impacts |
Ericsson |
| 5.30.3.2 |
Timing requirements for UL multi-DCI multi-TRP with two TAs |
|
| R4-2304057 |
Discussion on timing requirements for UL multi-DCI multi-TRP with two TAs |
Nokia, Nokia Shanghai Bell |
| R4-2304301 |
On R18 eFeMIMO - MTTD for multi-DCI mult-TRP with two TAs |
Apple |
| R4-2304743 |
Discussion on timing requirements for Multi-DCI multi-TRP with two TAs |
Samsung |
| R4-2304788 |
on the MTTD for two TAs |
Xiaomi |
| R4-2304814 |
Discussion on maximum uplink timing difference for multi-DCI multi-TRP with two TAs |
vivo |
| R4-2304832 |
On timing requirements for MIMO evolution |
Ericsson |
| R4-2304921 |
Discussion on R18 MIMO for Timing requirements for UL multi-DCI multi-TRP with two Tas |
MediaTek Inc. |
| R4-2305001 |
Discussion on the Timing requirements for UL multi-DCI multi-TRP with two TAs |
ZTE Corporation |
| R4-2305323 |
Discussion on RRM requirements for multi-DCI multi-TRP with two TAs |
Huawei, HiSilicon |
| 5.30.3.3 |
Unified TCI framework |
|
| R4-2304058 |
Discussion on Rel-18 extension of Unified TCI framework for mTRP operation |
Nokia, Nokia Shanghai Bell |
| R4-2304145 |
On RRM requirements for unified TCI framework with mTRP |
Apple |
| R4-2304248 |
Discussion on FeMIMO Unified TCI framework RRM impacts |
Intel Corporation |
| R4-2304744 |
Discussion on enhanced unified TCI framework in Rel-18 MIMO evolution for downlink and uplink |
Samsung |
| R4-2304787 |
on the Unified TCI framework |
Xiaomi |
| R4-2304815 |
Discussion on RRM impacts from R18 enhancement of TCI framework |
vivo |
| R4-2304922 |
Discussion on R18 MIMO for Unified TCI framework |
MediaTek Inc. |
| R4-2305273 |
Discussion on RRM requirements for Rel-18 MIMO_uTCI |
Huawei, HiSilicon |
| R4-2305765 |
Discussion on unified TCI state switch requirements for mTRP |
Ericsson |
| 5.30.4 |
Moderator summary and conclusions |
|
| R4-2304302 |
LS on MTTD for multi-DCI mult-TRP with two TAs |
Apple |
| R4-2306171 |
Topic summary for [106-bis-e][223] NR_MIMO_evo_DL_UL |
Moderator (Samsung) |
| R4-2306222 |
Topic summary for [106-bis-e][143] NR_MIMO_evo_DL_UL_UERF |
Moderator (Samsung) |
| R4-2306254 |
Topic summary for [106-bis-e][223] NR_MIMO_evo_DL_UL |
Moderator (Samsung) |
| R4-2306305 |
Topic summary for [106-bis-e][143] NR_MIMO_evo_DL_UL_UERF |
Moderator (Samsung) |
| R4-2306361 |
LS on MTTD for multi-DCI mult-TRP with two TAs |
Apple |
| R4-2306362 |
WF on R18 NR MIMO RRM requirements |
Samsung |
| R4-2306629 |
WF on UE RF requirements on STxMP |
Samsung |
| 5.31.1 |
General and work plan |
|
| R4-2304460 |
Considerations regarding sidelink operation in unlicensed bands |
CableLabs |
| R4-2304700 |
Revised Work plan for RRM part on Rel-18 NR Sidelink Evolution |
LG Electronics Inc., OPPO |
| R4-2305421 |
Updated RF workplan for NR SL evolution |
OPPO, LGE, Huawei |
| R4-2305422 |
TR38.786 v0.1.0 for SL evoluation |
OPPO |
| R4-2305423 |
R18 SL-U requirement location in 38101-1 |
OPPO |
| R4-2305817 |
Sidelink general aspects |
Qualcomm Incorporated |
| 5.31.2.1 |
Sidelink on a single unlicensed spectrum |
|
| R4-2305456 |
Discussion on Sidelink on a single unlicensed spectrum |
Huawei, HiSilicon |
| 5.31.2.1.1 |
System parameters (channel bandwidth, channel arrangement) |
|
| R4-2304485 |
On System parameters (channel bandwidth, channel arrangement) for NR sidelink evolution |
LG Electronics Finland |
| R4-2304952 |
On system parameters for sidelink in unlicensed spectrum |
Nokia, Nokia Shanghai Bell |
| R4-2305078 |
Discussion on system parameters for SL on a single unlicensed spectrum |
vivo |
| R4-2305424 |
R18 SL-U single CC system parameters |
OPPO |
| R4-2305457 |
Discussion on system parameter for sidelink on a single unlicensed spectrum |
Huawei, HiSilicon |
| R4-2305523 |
on the SL-e system parameter |
Xiaomi |
| R4-2305815 |
System parameters for unlicensed sidelink |
Qualcomm Incorporated |
| 5.31.2.1.2 |
Tx requirements |
|
| R4-2304184 |
MPR simulation assumptions and other Tx requirements for SL-U in Rel-18 |
Meta Ireland |
| R4-2304486 |
On Tx requirements for NR sidelink evolution |
LG Electronics Finland |
| R4-2304953 |
On UE Tx requirements for sidelink in unlicensed spectrum |
Nokia, Nokia Shanghai Bell |
| R4-2305079 |
Discussion on UE RF requirements for SL on a single unlicensed spectrum |
vivo |
| R4-2305425 |
R18 SL-U single CC Tx requirements |
OPPO |
| R4-2305524 |
on the SL-e TX requirement |
Xiaomi |
| R4-2305816 |
Sidelink UE TX requirements in unlicensed spectrum |
Qualcomm Incorporated |
| R4-2306634 |
on the SL-e TX requirement |
Xiaomi |
| 5.31.2.1.3 |
Rx requirements |
|
| R4-2304487 |
On Rx requirements for NR sidelink evolution |
LG Electronics Finland |
| R4-2304954 |
On UE Rx requirements for sidelink in unlicensed spectrum |
Nokia, Nokia Shanghai Bell |
| R4-2305426 |
R18 SL-U single CC Rx requirements |
OPPO |
| R4-2305522 |
on the SL-e RX requirement |
Xiaomi |
| R4-2306635 |
on the SL-e RX requirement |
Xiaomi |
| 5.31.2.2 |
Con-current operation on Uu and sidelink |
|
| R4-2304183 |
Con-current operation with NR Uu and SL-U in Rel-18 |
Meta Ireland |
| R4-2304606 |
UE RF requirements of con-current operation on Uu and sidelink |
LG Electronics |
| R4-2305427 |
R18 SL-U concurrent operation |
OPPO |
| R4-2305458 |
On inter-band con-current operation on Uu and sidelink |
Huawei, HiSilicon |
| R4-2305520 |
on con-current operation on Uu and sidelink |
Xiaomi |
| R4-2305818 |
Concurrent operation and Uu and sidelink UE considerations |
Qualcomm Incorporated |
| 5.31.2.3 |
Sidelink CA |
|
| R4-2304185 |
Consideration on example RF architecture and MPR/A-MPR assumptions for Intra-band contiguous SL CA in band n47 |
Meta Ireland |
| R4-2304607 |
Discussion on UE RF requirements of SL CA |
LG Electronics |
| R4-2304955 |
On NR sidelink CA RF |
Nokia, Nokia Shanghai Bell |
| R4-2305080 |
Discussion on SL CA |
vivo |
| R4-2305428 |
R18 SL CA |
OPPO |
| R4-2305459 |
On sidelink CA |
Huawei, HiSilicon |
| R4-2305521 |
on sidelink CA |
Xiaomi |
| R4-2305819 |
UE requirements and sidelink CA in n47 |
Qualcomm Incorporated |
| 5.31.2.4 |
Co-channel coexistence for LTE sidelink and NR sidelink |
|
| R4-2304488 |
On Co-channel coexistence for LTE SL and NR SL |
LG Electronics Finland |
| R4-2304956 |
On Co-channel coexistence between NR sidelink and LTE sidelink |
Nokia, Nokia Shanghai Bell |
| R4-2305460 |
Co-channel coexistence for LTE sidelink and NR sidelink |
Huawei, HiSilicon |
| R4-2305519 |
on co-channel coexistence for LTE sidelink and NR sidelink |
Xiaomi |
| 5.31.3 |
RRM core requirements |
|
| R4-2304929 |
Discussion on RRM impacts for R18 NR Sidelink evolution |
MediaTek Inc. |
| R4-2305324 |
Discussion on RRM impacts for R18 sidelink evolution |
Huawei, HiSilicon |
| 5.31.3.1 |
Sidelink CA |
|
| R4-2304701 |
Discussion on NR sidelink CA operation |
LG Electronics Inc. |
| R4-2304781 |
Discussion on RRM core requirements for sidelink CA |
Xiaomi |
| R4-2305245 |
On RRM requirements for NR SL CA |
OPPO |
| R4-2305545 |
Discussion on Rel. 18 NR sidelink CA enhancement impact on RRM requirements |
Nokia, Nokia Shanghai Bell |
| 5.31.3.2 |
SL unlicensed operation |
|
| R4-2304251 |
Discussion on RRM requirement for SL in unlicensed spectrum |
Intel Corporation |
| R4-2304356 |
SL enhancement RRM scope |
Qualcomm, Inc. |
| R4-2304702 |
Discussion on NR sidelink unlicensed operation |
LG Electronics Inc. |
| R4-2304782 |
Discussion on RRM core requirements for SL unlicensed operation |
Xiaomi |
| R4-2305246 |
On RRM requirements for NR SL-U |
OPPO |
| R4-2305546 |
Discussion of SL-U impacts on RRM requirements |
Nokia, Nokia Shanghai Bell |
| R4-2305731 |
Discussions on RRM requirements for sidelink evolution |
Ericsson |
| 5.31.3.3 |
Co-channel coexistence for LTE SL and NR SL |
|
| R4-2304703 |
Discussion on co-channel coexistence for LTE SL and NR SL |
LG Electronics Inc. |
| R4-2304783 |
Discussion on RRM core requirements for Co-channel coexistence for LTE SL and NR SL |
Xiaomi |
| R4-2305247 |
On RRM requirements for Co-channel coexistence for LTE SL and NR SL |
OPPO |
| R4-2305547 |
RRM requirements for co-channel coexistence for LTE sidelink and NR sidelink |
Nokia, Nokia Shanghai Bell |
| 5.31.4 |
Moderator summary and conclusions |
|
| R4-2306172 |
Topic summary for [106-bis-e][224] NR_SL_enh2_part1 |
Moderator (LGE) |
| R4-2306173 |
Topic summary for [106-bis-e][225] NR_SL_enh2_part2 |
Moderator (OPPO) |
| R4-2306223 |
Topic summary for [106-bis-e][144] NR_SL_enh2_UERF_part1 |
Moderator (OPPO_ |
| R4-2306224 |
Topic summary for [106-bis-e][145] NR_SL_enh2_UERF_part2 |
Moderator (LGE) |
| R4-2306225 |
Topic summary for [106-bis-e][146] NR_SL_enh2_UERF_part3 |
Moderator (Huawei) |
| R4-2306255 |
Topic summary for [106-bis-e][224] NR_SL_enh2_part1 |
Moderator (LGE) |
| R4-2306256 |
Topic summary for [106-bis-e][225] NR_SL_enh2_part2 |
Moderator (OPPO) |
| R4-2306306 |
Topic summary for [106-bis-e][144] NR_SL_enh2_UERF_part1 |
Moderator (OPPO_ |
| R4-2306307 |
Topic summary for [106-bis-e][145] NR_SL_enh2_UERF_part2 |
Moderator (LGE) |
| R4-2306308 |
Topic summary for [106-bis-e][146] NR_SL_enh2_UERF_part3 |
Moderator (Huawei) |
| R4-2306363 |
WF on RRM requirements for NR sidelink unlicensed operation |
LGE |
| R4-2306364 |
WF on RRM requirements for NR Sidelink CA and co-channel co-existence for LTE SL and NR SL |
OPPO |
| R4-2306630 |
WF on SLU single CC system parameters |
Vivo |
| R4-2306631 |
WF on SLU single CC Tx requirements |
Xiaomi |
| R4-2306632 |
WF on WF on SLU single CC Rx requirements |
OPPO |
| R4-2306633 |
WF on MPR simulation assumptions for SLU single CC |
Meta |
| R4-2306636 |
WF on NR SL con-current operation and co-channel coexistence scenario of LTE V2X and NR V2X |
LGE |
| R4-2306637 |
WF on SL CA |
Huawei, HiSilicon |
| 5.32.2 |
UE RF requirements |
|
| R4-2304355 |
eRedCap UE REFSENS |
Apple |
| R4-2305072 |
Discussion on UE RF requirements for eRedcap |
Xiaomi |
| R4-2305385 |
Discussion on RF impacts for R18 RedCap UE |
Huawei, HiSilicon |
| R4-2305501 |
eRedCap UE RF impacts |
Qualcomm Inc. |
| R4-2305549 |
Discussion on Rel-18 NR sidelink relay enhancements |
Nokia, Nokia Shanghai Bell |
| R4-2305646 |
Remaining Redcap RF issue |
Ericsson |
| R4-2305647 |
CR for REFSENS for eRedcap UE |
Ericsson |
| R4-2305695 |
UE RF requirements for Enhanced RedCap |
Nokia, Nokia Shanghai Bell |
| 5.32.3 |
BS RF requirements |
|
| R4-2305651 |
BS RF requirements for Enhanced RedCap |
Nokia, Nokia Shanghai Bell |
| 5.32.4 |
RRM core requirements |
|
| R4-2304153 |
RRM for eRedCap |
Apple |
| R4-2304169 |
Discussion on impacts to RRM core requirements for Enhanced RedCap |
ZTE Corporation |
| R4-2304415 |
Discussion on RRM requirements for eRedCap |
CATT |
| R4-2304515 |
Consideration on RRM requirements for Redcap enhancement |
vivo |
| R4-2304598 |
Discussion on further NR RedCap UE complexity reduction |
MediaTek inc. |
| R4-2304784 |
Discussion on RRM core requirements for eRedCap |
Xiaomi |
| R4-2305286 |
Discussion on RRM impact for Enhanced support of reduced capability NR devices |
Huawei, HiSilicon |
| R4-2305569 |
RRM core requirements for Enhanced RedCap |
Nokia, Nokia Shanghai Bell |
| R4-2305732 |
Discussions on enhanced RedCap RRM impact |
Ericsson |
| R4-2305802 |
eDRX requirements for R18 eRedCap |
Qualcomm Incorporated |
| 5.32.5 |
Moderator summary and conclusions |
|
| R4-2306174 |
Topic summary for [106-bis-e][226] NR_redcap_enh |
Moderator (Ericsson) |
| R4-2306226 |
Topic summary for [106-bis-e][147] NR_redcap_enh_UERF |
Moderator (Ericsson) |
| R4-2306257 |
Topic summary for [106-bis-e][226] NR_redcap_enh |
Moderator (Ericsson) |
| R4-2306309 |
Topic summary for [106-bis-e][147] NR_redcap_enh_UERF |
Moderator (Ericsson) |
| R4-2306365 |
WF on R18 RedCap RRM requirements |
Ericsson |
| R4-2306638 |
WF on eRedCap UE RF requirements |
Ericsson |
| 5.33.1 |
General and work plan |
|
| R4-2304357 |
SL relay LS reply discussion |
Qualcomm, Inc. |
| R4-2304785 |
Discussion on RRM core requirement for enhanced NR sidelink relay |
Xiaomi |
| R4-2304912 |
Discussion on incoming LS on comparison of SL-RSRP and SD RSRP measurements |
LG Electronics UK |
| R4-2304930 |
Discussion on SL-RSRP and SD-RSRP |
MediaTek Inc. |
| R4-2304931 |
Draft reply LS on Comparison of SL-RSRP and SD-RSRP measurements |
MediaTek Inc. |
| R4-2305226 |
Discussion on comparison of SL-RSRP and SD-RSRP measurements |
OPPO |
| R4-2305548 |
Reply LS on Comparison of SL-RSRP and SD-RSRP measurements (R2-2302234 ) |
Nokia, Nokia Shanghai Bell |
| 5.33.2 |
RRM core requirements |
|
| R4-2304786 |
Discussion on RRM core requirement for enhanced NR sidelink relay |
Xiaomi |
| R4-2304913 |
Discussion on Rel-18 NR sidelink relay enhancements |
LG Electronics UK |
| R4-2304932 |
Discussion on RRM impacts for R18 NR sidelink relay enhancements |
MediaTek Inc. |
| R4-2305325 |
Discussion on RRM impacts for R18 sidelink relay enhancement |
Huawei, HiSilicon |
| R4-2305792 |
Analysis of RRM requirements for SL relay enhancement |
Ericsson |
| R4-2305793 |
LS response on comparison of SL-RSRP and SD-RSRP measurements |
Ericsson |
| 5.33.3 |
Moderator summary and conclusions |
|
| R4-2306175 |
Topic summary for [106-bis-e][227] NR_SL_relay_enh |
Moderator (LGE) |
| R4-2306258 |
Topic summary for [106-bis-e][227] NR_SL_relay_enh |
Moderator (LGE) |
| R4-2306366 |
Reply LS on Comparison of SL-RSRP and SDRSRP measurements |
Nokia, Nokia Shanghai Bell |
| R4-2306367 |
WF on RRM requirements for NR SL relay enhancements |
LGE |
| 5.34.2 |
Co-existence study |
|
| R4-2304451 |
Discussion on the co-existence study for mIAB for NR |
Qualcomm CDMA Technologies |
| R4-2304527 |
Discussion on mobile IAB co-existence |
Nokia, Nokia Shanghai Bell |
| R4-2305633 |
Discussion on Mobile IAB co-ex study |
Samsung |
| R4-2305642 |
Coexisting study simulation assumptions |
Ericsson |
| 5.34.3 |
RF core requirements |
|
| R4-2304528 |
Considerations on mobile IAB RF requirements |
Nokia, Nokia Shanghai Bell |
| 5.34.4 |
RRM core requirements |
|
| R4-2304280 |
On Mobile IAB RRM Core Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2305272 |
Discussion on RRM impact on Rel-18 mobile IAB |
Huawei, HiSilicon |
| R4-2305791 |
Analysis of RRM requirements for mobile IAB |
Ericsson |
| 5.34.5 |
Moderator summary and conclusions |
|
| R4-2305861 |
Topic Summary [106bis-e][314] NR_mobile_IAB_RF |
Moderator (Qualcomm) |
| R4-2305935 |
WF on mIAB RF requirements and coexistence |
Qualcomm |
| R4-2305984 |
Topic Summary [106bis-e][314] NR_mobile_IAB_RF |
Moderator (Qualcomm) |
| R4-2306176 |
Topic summary for [106-bis-e][228] NR_mobile_IAB |
Moderator (Qualcomm) |
| R4-2306259 |
Topic summary for [106-bis-e][228] NR_mobile_IAB |
Moderator (Qualcomm) |
| R4-2306368 |
WF on RRM requirements for mobile IAB |
Qualcomm Incorporated |
| 5.35.1 |
General and work plan |
|
| R4-2304180 |
Feasibility study of SSB-less SCell operation for FR1 inter-band co-located CA |
Nokia, Nokia Shanghai Bell |
| R4-2305288 |
Work plan on network energy savings for NR |
Huawei, HiSilicon |
| R4-2306391 |
Work plan on network energy savings for NR |
Huawei, HiSilicon |
| R4-2306640 |
Work plan on network energy savings for NR |
Huawei, HiSilicon |
| 5.35.2 |
BS and UE RF requirements |
|
| R4-2304212 |
Discussion on synchronization and RF requirements |
CMCC |
| R4-2304221 |
Discussion on feasibility of SSB-less SCell operation for inter-band CA for FR1 and co-located cells |
Huawei, Hisilicon |
| R4-2304448 |
Discussion on BS RF requirement for network energy saving for NR |
CATT |
| R4-2304534 |
RF requirements for Network energy savings for NR |
Nokia, Nokia Shanghai Bell |
| R4-2305025 |
RF aspects on SSB-less SCell operation for FR1 inter-band CA |
China Telecom |
| R4-2305529 |
Discussion on RF requirement impacts from NES perspective |
ZTE Corporation |
| 5.35.3 |
RRM core requirements |
|
| R4-2304155 |
On RRM requirements for NES |
Apple |
| R4-2304181 |
SSB-less operation for FR1 inter-band co-located CA |
Nokia, Nokia Shanghai Bell |
| R4-2304229 |
NR network energy saving RRM aspects |
Intel Corporation |
| R4-2304387 |
Discussion on requirements of SSBless Scell at inter-band CA for FR1 |
Qualcomm Incorporated |
| R4-2304647 |
Discussion on RRM impaction for network energy saving |
CMCC |
| R4-2304816 |
Discussion on SSB-less SCell operation for network energy saving |
vivo |
| R4-2304893 |
Discussion on general aspects in NES |
Ericsson |
| R4-2305002 |
Discussion on RRM aspects of Network energy saving for NR |
ZTE Corporation |
| R4-2305026 |
RRM requirements on SSB-less SCell operation for FR1 inter-band CA |
China Telecom |
| R4-2305157 |
Expected RRM requirements for network energy saving |
MediaTek inc. |
| R4-2305289 |
Discussion on RRM impact for network energy savings for NR |
Huawei, HiSilicon |
| R4-2305544 |
Expected RRM requirements for network energy saving |
MediaTek Inc. |
| 5.35.4 |
Moderator summary and conclusions |
|
| R4-2306177 |
Topic summary for [106-bis-e][229] Netw_Energy_NR |
Moderator (Huawei) |
| R4-2306227 |
Topic summary for [106-bis-e][148] Netw_Energy_NR |
Moderator (Huawei) |
| R4-2306260 |
Topic summary for [106-bis-e][229] Netw_Energy_NR |
Moderator (Huawei) |
| R4-2306310 |
Topic summary for [106-bis-e][148] Netw_Energy_NR |
Moderator (Huawei) |
| R4-2306369 |
WF on RRM requirements for NR network energy saving |
Huawei, HiSilicon |
| R4-2306639 |
WF on RF feasibility study of NR Network Energy Saving |
Huawei, HiSilicon |
| 5.36.1 |
General and work plan |
|
| R4-2304507 |
Discussion on UAV requirements |
Nokia, Nokia Shanghai Bell |
| 5.36.2 |
Necessary UE types and additional OOBE requirements for aerial UEs |
|
| R4-2304211 |
Discussion on NR UAV requirements |
CMCC |
| R4-2304362 |
UAV emissions for EU |
Qualcomm Incorporated |
| R4-2304508 |
Discussion on UAV Arial UE Type(s) |
Nokia, Nokia Shanghai Bell |
| R4-2304577 |
Additional UE OOBE for UAV in 1.7 and 2.5 GHz |
Ericsson |
| R4-2304578 |
Draft CR to TS 38.101-1 - Additional OOBE for Aerial Ues in CEPT countries |
Ericsson |
| R4-2305712 |
Initial discussion on additional OOBE requirements for aerial UEs |
Huawei, HiSilicon |
| R4-2305713 |
Draft CR to TS 38.101-1 on additional OOBE requirements for aerial UEs |
Huawei, HiSilicon |
| R4-2305714 |
Draft CR to TS 36.101 on additional OOBE requirements for aerial UEs |
Huawei, HiSilicon |
| 5.36.3 |
Moderator summary and conclusions |
|
| R4-2306228 |
Topic summary for [106-bis-e][149] NR_UAV |
Moderator (Nokia) |
| R4-2306311 |
Topic summary for [106-bis-e][149] NR_UAV |
Moderator (Nokia) |
| R4-2306641 |
WF on NR support for UAV |
Nokia |
| R4-2306642 |
WF on back off study (MPR/A-MPR) for UAV |
Qualcomm |
| R4-2306643 |
Running Draft CR to TS 38.101-1 on additional OOBE requirements for aerial UEs |
Ericsson |
| R4-2306644 |
Running Draft CR to TS 36.101 on additional OOBE requirements for aerial UEs |
Huawei, HiSilicon |
| 6.1.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2304512 |
Big CR on Introduction of completed R18 x(x<=6) DL y(y<=2) UL CA band combinations to TS 36.101 |
Huawei Technologies France |
| R4-2304513 |
Revised WID Rel-18 LTE-A CA for x(x<=6) DL y(y<=2) UL |
Huawei Technologies France |
| R4-2304514 |
TR 36.718-02-01 LTE-A CA for x(x=123456) DL y(y=12) UL |
Huawei Technologies France |
| 6.1.2.1 |
Requirements with specific issues |
|
| R4-2304965 |
TP to TR 36.718-02-01 Addition of CA_2A-4A-28A w ULCA.docx |
Nokia |
| R4-2306532 |
TP to TR 36.718-02-01 Addition of CA_2A-4A-28A w ULCA.docx |
Nokia |
| 6.1.2.2 |
Requirements without specific issues |
|
| R4-2304964 |
TP to TR 36.718-02-01 Addition of CA_2A-28A w ULCA.docx |
Nokia |
| 6.1.4 |
Moderator summary and conclusions |
|
| R4-2306185 |
Topic summary for [106-bis-e][105] LTE_Baskets |
Moderator (Huawei) |
| R4-2306268 |
Topic summary for [106-bis-e][105] LTE_Baskets |
Moderator (Huawei) |
| 6.3.2 |
Band definition and system parameters |
|
| R4-2304878 |
Discussion on Band definition |
Nokia, Nokia Shanghai Bell |
| R4-2305351 |
Discussion on band definition for LTE based broadcast |
ZTE Corporation |
| R4-2305823 |
Considerations for multi-filter UE full-band UHF support |
Qualcomm Incorporated |
| 6.3.3 |
UE RF requirements |
|
| R4-2304461 |
UHF band allocation for 5G Broadcast: some proposals based on existing UE filter’s technology |
SWR |
| R4-2304511 |
Discussion on RF requirements for 5G Broadcast |
Mediatek India Technology Pvt. |
| R4-2304879 |
LTE based 5G UE RF open issues |
Nokia, Nokia Shanghai Bell |
| R4-2305382 |
Discussion on UE RF requirements |
Huawei, HiSilicon |
| R4-2305822 |
An update on in-channel ACS for 5G broadcast |
Qualcomm Incorporated |
| R4-2305824 |
Introduction of 5G broadcast UHF bands – Clauses 3, 4, and 5 |
Qualcomm Incorporated |
| R4-2306568 |
Introduction of 5G broadcast UHF bands – Clauses 3, 4, and 5 |
Qualcomm Incorporated |
| 6.3.5 |
Moderator summary and conclusions |
|
| R4-2306196 |
Topic summary for [106-bis-e][116] LTE_terr_bcast_bands_UERF |
Moderator (Qualcomm) |
| R4-2306279 |
Topic summary for [106-bis-e][116] LTE_terr_bcast_bands_UERF |
Moderator (Qualcomm) |
| R4-2306566 |
WF on UE RF requirements for 5G broadcast |
Qualcomm |
| R4-2306567 |
LS on the impact of PMCH RMC’s for 5G broadcast |
Apple |
| 6.4.2 |
Band definition and co-existence requirements |
|
| R4-2305355 |
draft CR to TS36.101 the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2305821 |
900 MHz band coexistence with Band 5/26 |
Qualcomm Incorporated |
| 6.4.3 |
UE RF requirements |
|
| R4-2305121 |
draft CR to TS 36.133: Introduction of 900 MHz LTE Band in the US |
ZTE Corporation |
| 6.4.4 |
BS RF requirements |
|
| R4-2304222 |
BS RF requirements for US 900 MHz LTE |
Huawei, Hisilicon |
| R4-2305356 |
CR to TS36.141 the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2305357 |
CR to TS37.141 the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2305358 |
CR to TS37.145-1 the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2305359 |
CR to TS37.145-2 the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2305360 |
CR to TS38.141-1 the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2305578 |
draftCR to 36.104 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2305579 |
draftCR to 36.141 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2305580 |
draftCR to 37.104 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2305581 |
draftCR to 37.141 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2305582 |
draftCR to 38.104 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2305583 |
draftCR to 38.141-1 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2305584 |
draftCR to 38.141-2 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2305837 |
CR to TS36.141: the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2305838 |
CR to TS37.141: the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2305839 |
CR to TS37.145-1: the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2305840 |
CR to TS37.145-2: the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2305841 |
CR to TS38.141-1: the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2306570 |
draftCR to 36.104 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2306571 |
draftCR to 36.141 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2306572 |
draftCR to 37.104 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2306573 |
draftCR to 38.104 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2306574 |
draftCR to 38.141-1 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2306575 |
draftCR to 38.141-2 on introduction of Band 106 |
Nokia, Nokia Shanghai Bell |
| R4-2306576 |
CR to TS37.141: the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2306577 |
CR to TS37.145-1: the introduction of 900 MHz LTE new band |
ZTE Corporation |
| R4-2306578 |
CR to TS37.145-2: the introduction of 900 MHz LTE new band |
ZTE Corporation |
| 6.4.5 |
Moderator summary and conclusions |
|
| R4-2306197 |
Topic summary for [106-bis-e][117] LTE_NR_US_900MHz |
Moderator (Qualcomm) |
| R4-2306280 |
Topic summary for [106-bis-e][117] LTE_NR_US_900MHz |
Moderator (Qualcomm) |
| R4-2306569 |
WF on UE RF requirements of US 900 MHz band |
Anterix |
| 6.5.2 |
Band definition and system parameters |
|
| R4-2305825 |
Extended L band for LTE NB-IoT |
Qualcomm Incorporated |
| 6.5.3 |
UE RF requirements |
|
| R4-2304492 |
Discussion on NTN FDD band (extended L band) UE RF requirements |
Mediatek India Technology Pvt. |
| R4-2304798 |
Discussion on UE RF requirements for the Extended L-band |
ZTE Corporation |
| R4-2304799 |
Draft CR to TS36.102 Introduction of the Extended L-band |
ZTE Corporation |
| 6.5.4 |
SAN RF requirements |
|
| R4-2304800 |
Discussion on SAN RF requirements for the Extended L-band |
ZTE Corporation |
| R4-2304801 |
Draft CR to TS36.108 Introduction of the Extended L-band |
ZTE Corporation |
| 6.5.6 |
Moderator summary and conclusions |
|
| R4-2306198 |
Topic summary for [106-bis-e][118] IoT_NTN_extLband |
Moderator (Inmarsat) |
| R4-2306281 |
Topic summary for [106-bis-e][118] IoT_NTN_extLband |
Moderator (Inmarsat) |
| R4-2306556 |
WF on IoT NTN Extended L-band |
Inmarsat |
| R4-2306658 |
WF on IoT NTN Extended L-band |
Inmarsat |
| 6.6.1 |
General and work plan |
|
| R4-2304496 |
Workplan for IoT NTN FDD LS band |
Mediatek India Technology Pvt. |
| R4-2304497 |
Draft of TR Skeleton for IoT NTN bands |
Mediatek India Technology Pvt. |
| R4-2306581 |
Workplan for IoT NTN FDD LS band |
Mediatek India Technology Pvt. |
| 6.6.2 |
Band definition and system parameters |
|
| R4-2305698 |
System parameters for L+S band for IoT NTN |
MediaTek Inc. |
| 6.6.3 |
UE RF requirements |
|
| R4-2304491 |
Discussion on NTN FDD band (L+S band) UE RF requirements |
Mediatek India Technology Pvt. |
| R4-2304802 |
Discussion on UE RF requirements for FDD band (L+S band) for IoT NTN operation |
ZTE Corporation |
| R4-2304803 |
Draft CR to TS36.102 Introduction of a new FDD band (L+S band) for IoT NTN operation |
ZTE Corporation |
| R4-2306580 |
Draft CR to TS36.102 Introduction of a new FDD band (L+S band) for IoT NTN operation |
ZTE Corporation |
| 6.6.4 |
SAN RF requirements |
|
| R4-2304804 |
Discussion on SAN RF requirements for FDD band (L+S band) for IoT NTN operation |
ZTE Corporation |
| R4-2304805 |
Draft CR to TS36.108 Introduction of a new FDD band (L+S band) for IoT NTN operation |
ZTE Corporation |
| R4-2306656 |
Draft CR to TS36.108 Introduction of a new FDD band (L+S band) for IoT NTN operation |
ZTE Corporation |
| 6.6.6 |
Moderator summary and conclusions |
|
| R4-2306199 |
Topic summary for [106-bis-e][119] IoT_NTN_FDD_LS_band |
Moderator (MediaTek) |
| R4-2306282 |
Topic summary for [106-bis-e][119] IoT_NTN_FDD_LS_band |
Moderator (MediaTek) |
| R4-2306579 |
WF on IoT_NTN_FDD_LS_band |
MediaTek |
| 6.7.2 |
UE RF requirements |
|
| R4-2305751 |
1.4MHz and 3MHz REFSENS for 600MHz US LTE band |
Skyworks Solutions Inc. |
| 6.7.4 |
RRM core requirements |
|
| R4-2305577 |
draftCR to 36.104 on introduction of Band 107 |
Nokia, Nokia Shanghai Bell |
| 6.8.3.1 |
General and work split |
|
| R4-2305715 |
Work-split arrangement for TS 36.181 development |
Huawei, HiSilicon |
| 6.8.3.5 |
TPs to draft TS 36.181 |
|
| R4-2304713 |
TP to TS 36.181: ACLR and OTA ACLR sections |
NEC |
| R4-2304714 |
TP to TS 36.181: OBUE and OTA OBUE sections |
NEC |
| R4-2304715 |
TP to TS 36.181: In-channel selectivity and OTA in-channel selectivity sections |
NEC |
| R4-2304716 |
TP to TS 36.181: Reference measurement channels |
NEC |
| R4-2305403 |
TP for TS 36.181: Clause 4.2~4.5 |
ZTE Corporation |
| R4-2305404 |
TP for TS 36.181: Clause 4.7~4.8 |
ZTE Corporation |
| R4-2305405 |
TP for TS 36.181: Clause 4.9 |
ZTE Corporation |
| R4-2305406 |
TP for TS 36.181: Clause 6.3 and 9.4 |
ZTE Corporation |
| R4-2305407 |
TP for TS 36.181: Clause 7.3 and 10.4 |
ZTE Corporation |
| R4-2305408 |
TP for TS 36.181: Clause 7.4 and 10.5 |
ZTE Corporation |
| R4-2305409 |
TP for TS 36.81: Annex D |
ZTE Corporation |
| R4-2305716 |
TP to TS 36.181: General sections |
Huawei, HiSilicon |
| R4-2305717 |
Big TP to TS 36.181 SAN conformance testing |
Huawei, HiSilicon |
| R4-2305718 |
TP to TS 36.181: Annex B |
Huawei, HiSilicon |
| R4-2305719 |
TP to TS 36.181: MU and TT values |
Huawei, HiSilicon |
| R4-2305720 |
TP to TS 36.181: Manufacturer declarations (4.6) |
Huawei, HiSilicon |
| R4-2305721 |
TP to TS 36.181: Requirements for (non-)contiguous spectrum, multi-band, and Reference coordinate system (4.10, 4.11, 4.12) |
Huawei, HiSilicon |
| R4-2305722 |
TP to TS 36.181: Conducted and OTA SAN output power (6.1, 6.2, 9.1, 9.2, 9.3) |
Huawei, HiSilicon |
| R4-2305723 |
TP to TS 36.181: Conducted and OTA Tx signal quality (6.5, 9.6, Annex F) |
Huawei, HiSilicon |
| R4-2305724 |
TP to TS 36.181: Conducted and OTA unwanted emissions: OBW (6.6.1, 6.6.2, 9.7.1, 9.7.2) |
Huawei, HiSilicon |
| R4-2305725 |
TP to TS 36.181: Conducted and OTA Tx spur (6.6.5, 9.7.5) |
Huawei, HiSilicon |
| R4-2305726 |
TP to TS 36.181: Conducted and OTA Refsens (7.1, 7.2, 10.1, 10.2, 10.3) |
Huawei, HiSilicon |
| R4-2305727 |
TP to TS 36.181: Conducted and OTA OOB blocking (7.5, 10.6) |
Huawei, HiSilicon |
| R4-2305937 |
TP for TS 36.181: Clause 4.2~4.5 |
ZTE Corporation |
| R4-2305938 |
TP for TS 36.181: Clause 4.7~4.8 |
ZTE Corporation |
| R4-2305939 |
TP for TS 36.181: Clause 4.9 |
ZTE Corporation |
| R4-2305940 |
TP for TS 36.181: Clause 6.3 and 9.4 |
ZTE Corporation |
| R4-2305941 |
TP for TS 36.181: Clause 7.3 and 10.4 |
ZTE Corporation |
| R4-2305942 |
TP for TS 36.181: Clause 7.4 and 10.5 |
ZTE Corporation |
| R4-2305943 |
TP for TS 36.81: Annex D |
ZTE Corporation |
| R4-2305944 |
TP to TS 36.181: ACLR and OTA ACLR sections |
NEC |
| R4-2305945 |
TP to TS 36.181: OBUE and OTA OBUE sections |
NEC |
| R4-2305946 |
TP to TS 36.181: In-channel selectivity and OTA in-channel selectivity sections |
NEC |
| R4-2305947 |
TP to TS 36.181: Reference measurement channels |
NEC |
| R4-2305948 |
TP to TS 36.181: General sections |
Huawei, HiSilicon |
| R4-2305949 |
TS 36.181 SAN conformance testing |
Huawei, HiSilicon |
| R4-2305950 |
TP to TS 36.181: Annex B |
Huawei, HiSilicon |
| R4-2305951 |
TP to TS 36.181: MU and TT values |
Huawei, HiSilicon |
| R4-2305952 |
TP to TS 36.181: Manufacturer declarations (4.6) |
Huawei, HiSilicon |
| R4-2305953 |
TP to TS 36.181: Requirements for (non-)contiguous spectrum, multi-band, and Reference coordinate system (4.10, 4.11, 4.12) |
Huawei, HiSilicon |
| R4-2305954 |
TP to TS 36.181: Conducted and OTA SAN output power (6.1, 6.2, 9.1, 9.2, 9.3) |
Huawei, HiSilicon |
| R4-2305955 |
TP to TS 36.181: Conducted and OTA Tx signal quality (6.5, 9.6, Annex F) |
Huawei, HiSilicon |
| R4-2305956 |
TP to TS 36.181: Conducted and OTA unwanted emissions: OBW (6.6.1, 6.6.2, 9.7.1, 9.7.2) |
Huawei, HiSilicon |
| R4-2305957 |
TP to TS 36.181: Conducted and OTA Tx spur (6.6.5, 9.7.5) |
Huawei, HiSilicon |
| R4-2305958 |
TP to TS 36.181: Conducted and OTA Refsens (7.1, 7.2, 10.1, 10.2, 10.3) |
Huawei, HiSilicon |
| R4-2305959 |
TP to TS 36.181: Conducted and OTA OOB blocking (7.5, 10.6) |
Huawei, HiSilicon |
| 6.8.4 |
UE RF requirement maintenance |
|
| R4-2304469 |
CR to 36.102 for A-MPR of NS_24 |
Sony |
| R4-2304489 |
Discussion on UE RF requirements for IoT NTN |
Mediatek India Technology Pvt. |
| R4-2304490 |
CR to 36.102 for NTN IoT UE RF requirements corrections |
MediaTek Inc. |
| R4-2305506 |
Handling of ETSI requirements |
Qualcomm Inc. |
| R4-2306646 |
CR to 36.102 for NTN IoT UE RF requirements corrections |
MediaTek Inc. |
| 6.8.5 |
RRM core requirement maintenance |
|
| R4-2304476 |
CR to TS 36.307 (Rel-17): release independence RRM requirements for IoT NTN |
Sony |
| R4-2304477 |
CR to TS 36.307 (Rel-18): release independence RRM requirements for IoT NTN |
Sony |
| R4-2304503 |
Discussion on remaining open issues for the Core Part of IoT NTN |
Nokia, Nokia Shanghai Bell |
| R4-2304648 |
Discussion on RRM core requirements maintenance for LTE NB-IoT and eMTC NTN |
CMCC |
| R4-2304819 |
RRM core requirements maintenance for LTE NB-IoT/eMTC over NTN |
MediaTek inc. |
| R4-2305259 |
Discussion on RRM requirements maintenance for IoT NTN |
Huawei, HiSilicon |
| R4-2305260 |
DraftCR on maintenance of NB-IoT for IoT NTN |
Huawei, HiSilicon |
| R4-2305652 |
CR on RRM core requirements maintenance for LTE NB-IoT/eMTC over NTN
Re-establishment |
MediaTek inc. |
| R4-2305734 |
Discussions on NTN IoT RRM requirements |
Ericsson |
| R4-2305738 |
Correction to IDLE mode cat-M IoT NTN requirements |
Ericsson |
| R4-2306372 |
CR to TS 36.307 (Rel-17): release independence RRM requirements for IoT NTN |
Sony |
| R4-2306373 |
DraftCR on maintenance of NB-IoT for IoT NTN |
Huawei, HiSilicon |
| R4-2306374 |
Correction to IDLE mode cat-M IoT NTN requirements |
Ericsson |
| R4-2306375 |
CR on RRM core requirements maintenance for LTE NB-IoT/eMTC over NTN Re-establishment |
MediaTek inc. |
| 6.8.6 |
RRM performance requirements |
|
| R4-2304374 |
draft Cat-B CR CQI for NB-IoT NTN |
Qualcomm Korea |
| R4-2304375 |
GNSS position acquisition method of IoT NTN |
Qualcomm Korea |
| R4-2304388 |
draft Cat-B CR CQI for NB-IoT NTN |
Qualcomm Korea |
| R4-2304504 |
Discussion on remaining open issues for the Perf. Part of IoT NTN |
Nokia, Nokia Shanghai Bell |
| R4-2304649 |
Discussion on RRM test cases for LTE NB-IoT and eMTC NTN |
CMCC |
| R4-2304650 |
draft CR on E-UTRAN RLM test for Cat-M1 UE in CEMode A in DRX |
CMCC |
| R4-2304820 |
Discussion on RRM performance requirement for IoT NTN |
MediaTek inc. |
| R4-2304821 |
Introduction of test cases of NB-IoT Radio Link Monitoring and reference configurations for satellite access |
MediaTek inc. |
| R4-2304822 |
Introduction of requirement for measurement accuracy and power headroom for Satellite Access |
MediaTek inc. |
| R4-2305060 |
DraftCR on TS 36.133 Random Access Test Cases for NB-IoT over NTN |
Nokia, Nokia Shanghai Bell |
| R4-2305061 |
DraftCR on TS 36.133 Timing Test Cases for eMTC over NTN |
Nokia, Nokia Shanghai Bell |
| R4-2305261 |
Discussion on performance requirements for IoT NTN |
Huawei, HiSilicon |
| R4-2305262 |
DraftCR on timing test cases of NB-IoT for IoT NTN |
Huawei, HiSilicon |
| R4-2305346 |
draftCR on TCs for random access for eMTC over NTN |
Huawei, HiSilicon |
| R4-2305653 |
Introduction of test cases of NB-IoT Radio Link Monitoring and reference configurations for satellite access |
MediaTek inc. |
| R4-2305654 |
Introduction of requirement for measurement accuracy and power headroom for Satellite Access |
MediaTek inc. |
| R4-2305735 |
Discussions on NTN IoT RRM performance requirements |
Ericsson |
| R4-2305736 |
RLM test cases for eMTC over NTN |
Ericsson |
| R4-2305737 |
Channel quality reporting accuracy test cases for eMTC over NTN |
Ericsson |
| R4-2305798 |
DraftCR on conditions for UE Cat-M1 bands in annex B |
Ericsson |
| R4-2305799 |
Draft CR on conditions for NB-IoT bands in annex B |
Ericsson |
| R4-2306376 |
Introduction of test cases of NB-IoT Radio Link Monitoring and reference configurations for satellite access |
MediaTek inc. |
| R4-2306377 |
draft Cat-B CR CQI for NB-IoT NTN |
Qualcomm Korea |
| R4-2306378 |
draftCR on TCs for random access for eMTC over NTN |
Huawei, HiSilicon |
| R4-2306379 |
DraftCR on TS 36.133 Timing Test Cases for eMTC over NTN |
Nokia, Nokia Shanghai Bell |
| R4-2306380 |
RLM test cases for eMTC over NTN |
Ericsson |
| R4-2306381 |
draft CR on E-UTRAN RLM test for Cat-M1 UE in CEMode A in DRX |
CMCC |
| R4-2306382 |
Channel quality reporting accuracy test cases for eMTC over NTN |
Ericsson |
| R4-2306383 |
DraftCR on conditions for UE Cat-M1 bands in annex B |
Ericsson |
| R4-2306384 |
Draft CR on conditions for NB-IoT bands in annex B |
Ericsson |
| R4-2306385 |
Introduction of requirement for measurement accuracy and power headroom for Satellite Access |
MediaTek inc. |
| 6.8.7.1 |
UE demodulation |
|
| R4-2304881 |
NTN NB-IoT/eMTC demodulation performance requirements |
Qualcomm India Pvt Ltd |
| R4-2304917 |
Draft CR to TS36.102, PDSCH requirements for NB-IoT over NTN |
MediaTek inc. |
| R4-2304918 |
Discussion on IoT-NTN UE demodulation requirements |
MediaTek inc. |
| R4-2304919 |
Summary of simulation results for IoT-NTN UE demodulation requirements |
MediaTek inc. |
| R4-2305175 |
Discussion on eMTC/NB-IoT UE demodulation requirements for NTN |
Ericsson |
| R4-2305176 |
draft CR: Introduction of eMTC UE demodulation requirements for NTN |
Ericsson |
| R4-2305488 |
Draft CR on IOT NTN demodulation performance requirements (TS36.102, Rel-18) |
Huawei,HiSilicon |
| R4-2305489 |
Simulation results on UE demodulation requirements for LTE NTN IOT |
Huawei,HiSilicon |
| R4-2305879 |
Draft CR to TS36.102, measurement channels for IoT-NTN |
Qualcomm |
| R4-2305962 |
Draft CR to TS36.102, PDSCH requirements for NB-IoT over NTN |
MediaTek inc. |
| R4-2305963 |
draft CR: Introduction of eMTC UE demodulation requirements for NTN |
Ericsson |
| R4-2305964 |
Draft CR on IOT NTN demodulation performance requirements (TS36.102, Rel-18) |
Huawei,HiSilicon |
| 6.8.7.2 |
SAN demodulation |
|
| R4-2304045 |
TP for 38.181 Introduction of SAN demodulation requirements for IoT-NTN |
Nokia, Nokia Shanghai Bell |
| R4-2304046 |
Comment on UL Pre-Compensation Gap and Number of Segments |
Nokia, Nokia Shanghai Bell |
| R4-2305177 |
Simulation results of SAN demodulation requirements for IoT-NTN |
Ericsson |
| R4-2305178 |
Discussion on SAN demodulation requirements for IoT-NTN |
Ericsson |
| R4-2305179 |
draft CR: Introduction of SAN demodulation requirements for IoT-NTN |
Ericsson |
| R4-2305180 |
Summary of SAN simulation results for IoT-NTN |
Ericsson |
| R4-2305490 |
Discussion on SAN demodulation requirements for LTE NTN IOT |
Huawei,HiSilicon |
| R4-2305491 |
Simulation results on SAN demodulation requirements for LTE NTN IOT |
Huawei,HiSilicon |
| R4-2305492 |
pCR on IOT NTN demodulation performance requirements (TS36.181, Rel-18) |
Huawei,HiSilicon |
| R4-2305536 |
Discussion and initial simulation results for eMTC and NB-IoT over NTN |
Samsung |
| R4-2305537 |
Draft CR on SAN demodulation requirements for NB-IoT over NTN |
Samsung |
| R4-2305961 |
Big CR to 36.102: Demodulation requirements for IoT-NTN |
MediaTek |
| R4-2305966 |
pCR for 36.181 Introduction of SAN demodulation requirements for IoT-NTN |
Nokia, Nokia Shanghai Bell |
| R4-2305967 |
pCR on IOT NTN demodulation performance requirements (TS36.181, Rel-18) |
Huawei,HiSilicon |
| R4-2305968 |
Draft CR on SAN demodulation requirements for NB-IoT over NTN |
Samsung |
| 6.8.8 |
Moderator summary and conclusions |
|
| R4-2305862 |
Topic Summary [106bis-e][316] IoT_NTN_SANRFConformance |
Moderator (Huawei) |
| R4-2305872 |
Topic Summary [106bis-e][326] IoT_NTN_Demod_Part1 |
Moderator (MediaTek) |
| R4-2305873 |
Topic Summary [106bis-e][327] IoT_NTN_Demod_Part2 |
Moderator (Ericsson) |
| R4-2305936 |
WF on remaining issues for the TS 36.181 drafting |
Huawei |
| R4-2305960 |
WF on IoT-NTN UE demodulation requirements |
MediaTek |
| R4-2305965 |
WF on IoT NTN SAN demodulation requirements |
Ericsson |
| R4-2305985 |
Topic Summary [106bis-e][316] IoT_NTN_SANRFConformance |
Moderator (Huawei) |
| R4-2305995 |
Topic Summary [106bis-e][326] IoT_NTN_Demod_Part1 |
Moderator (MediaTek) |
| R4-2305996 |
Topic Summary [106bis-e][327] IoT_NTN_Demod_Part2 |
Moderator (Ericsson) |
| R4-2306178 |
Topic summary for [106-bis-e][230] LTE_NBIOT_eMTC_NTN_req |
Moderator (MediaTek) |
| R4-2306261 |
Topic summary for [106-bis-e][230] LTE_NBIOT_eMTC_NTN_req |
Moderator (MediaTek) |
| R4-2306370 |
WF on NB-IoT/eMTC RRM requirements for NTN |
MediaTek |
| R4-2306371 |
LS on GNSS position acquisition in timing test |
Qualcomm |
| R4-2306386 |
Draft Big CR on NB-IoT/eMTC RRM performance requirements for NTN |
MediaTek |
| R4-2306645 |
WF on LTE_NBeMTC_NTN_UERF |
MediaTek |
| 6.9.4 |
RRM core requirements |
|
| R4-2304502 |
Discussion on Mobility Aspects and other core requirements for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R4-2304651 |
Discussion on RRM core requirements for IOT NTN enhancement |
CMCC |
| R4-2304823 |
Discussion on RRM requirements for IoT NTN enhancement |
MediaTek inc. |
| R4-2305263 |
Discussion on RRM requirements for IoT NTN enhancement |
Huawei, HiSilicon |
| R4-2305733 |
Discussions on RRM requirements for IoT NTN enhancements |
Ericsson |
| 6.9.5 |
Moderator summary and conclusions |
|
| R4-2306179 |
Topic summary for [106-bis-e][231] IoT_NTN_enh |
Moderator (MediaTek) |
| R4-2306229 |
Topic summary for [106-bis-e][150] LTE_NBeMTC_NTN_UERF |
Moderator (MediaTek) |
| R4-2306262 |
Topic summary for [106-bis-e][231] IoT_NTN_enh |
Moderator (MediaTek) |
| R4-2306312 |
Topic summary for [106-bis-e][150] LTE_NBeMTC_NTN_UERF |
Moderator (MediaTek) |
| R4-2306387 |
WF on RRM requirements for IoT NTN enhancements |
MediaTek |
| 7 |
Liaison and output to other groups |
|
| R4-2305679 |
Discussion on LS to RAN4 on autonomous denial for IDC |
Nokia Corporation |
| 7.1.1 |
On support of per FR PRS gap (R2-2213350) |
|
| R4-2304083 |
Consideration on support of per FR PRS gap |
vivo |
| R4-2304426 |
Discussion on support of per FR PRS gap |
CATT |
| R4-2305156 |
Discussion on LS on support of per FR PRS gap |
MediaTek inc. |
| R4-2305227 |
Discussion on support of per FR PRS gap |
OPPO |
| R4-2305347 |
Reply LS on support of per FR PRS gap |
Huawei, HiSilicon |
| R4-2305677 |
On per-FR gaps for NR positioning |
Qualcomm Incorporated |
| R4-2305690 |
Discussion on support of per-FR gap for PRS measurements |
Nokia, Nokia Shanghai Bell |
| R4-2305780 |
On perFR gap for positioning measurement |
Ericsson |
| 7.1.2 |
On enhanced cell reselection requirements in NTN (R2-2301966) |
|
| R4-2304427 |
Further response on enhanced cell reselection requirements in NTN |
CATT |
| R4-2304505 |
LS Reply on follow-up of NTN Cell Reselection |
Nokia, Nokia Shanghai Bell |
| R4-2304506 |
DraftCR on Cell Reselection for RRC Inactive in NTN |
Nokia, Nokia Shanghai Bell |
| R4-2304771 |
Reply LS on enhanced cell reselection requirement for NTN |
Xiaomi |
| R4-2304910 |
Discussion on enhanced cell reselection requirements in NTN |
LG Electronics UK |
| R4-2305036 |
LS to RAN2 on enhanced cell re-selection requirements in NTN |
ZTE Corporation |
| R4-2305063 |
DraftCR to TS 38.133 on Cell Reselection for RRC Inactive in NTN (Rel-17) |
Nokia, Nokia Shanghai Bell |
| R4-2305064 |
DraftCR to TS 38.133 on Cell Reselection for RRC Inactive in NTN (Rel-18) |
Nokia, Nokia Shanghai Bell |
| R4-2305189 |
Reply LS on enhanced cell reselection requirements in NTN in Agenda 7.1.2 |
Ericsson |
| R4-2305348 |
Reply LS on enhanced cell reselection requirements in NTN |
Huawei, HiSilicon |
| 7.1.3 |
Others |
|
| R4-2304659 |
Updated RAN4 Rel-17 features list |
CMCC |
| R4-2304660 |
LS on updated Rel-17 RAN4 feature list for NR |
CMCC |
| R4-2305062 |
Updated RAN4 Rel-17 features list |
Nokia, Nokia Shanghai Bell |
| R4-2305507 |
Draft reply LS on applicability of requirements for RedCap UE |
Qualcomm Inc. |
| 7.2.1 |
On Rel-16 UL Tx switching period (R1-2302198) |
|
| R4-2304127 |
Switching period ambiguity |
Qualcomm Incorporated |
| R4-2304337 |
Draft LS response on Rel-16 UL Tx Switching period |
Apple |
| R4-2304403 |
On the exact location of UL Tx switching period for Rel-16/17 |
China Telecom |
| R4-2304467 |
Draft Reply LS to RAN1 on Rel-16 UL Tx Switching period |
Ericsson |
| R4-2304945 |
On clarification to the switching period location of the UL Tx Switching |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R4-2304946 |
Rel-16 draftCR to 38 101-1 for Clarification of UL Tx Switching |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R4-2304947 |
Rel-17 draftCR to 38 101-1 for Clarification of UL Tx Switching |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R4-2304948 |
Rel-18 draftCR to 38 101-1 for Clarification of UL Tx Switching |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R4-2304949 |
Rel-16 draftCR to 38 101-3 for Clarification of UL Tx Switching |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R4-2304950 |
Rel-17 draftCR to 38 101-3 for Clarification of UL Tx Switching |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R4-2304951 |
Rel-18 draftCR to 38 101-3 for Clarification of UL Tx Switching |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R4-2305089 |
[Draft] Reply LS on Rel-16 UL Tx switching period |
vivo |
| R4-2305090 |
Draft CR for 38.101-1 for UL Tx switching period update (Rel-16) |
vivo |
| R4-2305091 |
Draft CR for 38.101-3 for UL Tx switching period update (Rel-16) |
vivo |
| R4-2305450 |
draftCR to 38.101-1: Clarification on the application of time mask for Tx switching (R16) |
Huawei, HiSilicon |
| R4-2305451 |
draftCR to 38.101-1: Clarification on the application of time mask for Tx switching (R17) |
Huawei, HiSilicon |
| R4-2305452 |
draftCR to 38.101-1: Clarification on the application of time mask for Tx switching (R18) |
Huawei, HiSilicon |
| R4-2305453 |
draftCR to 38.101-3: Clarification on the application of time mask for Tx switching (R16) |
Huawei, HiSilicon |
| R4-2305454 |
draftCR to 38.101-3: Clarification on the application of time mask for Tx switching (R17) |
Huawei, HiSilicon |
| R4-2305455 |
draftCR to 38.101-3: Clarification on the application of time mask for Tx switching (R18) |
Huawei, HiSilicon |
| R4-2305663 |
Discussion on Rel-16 time mask of Tx switching |
Huawei Technologies France |
| R4-2306647 |
Rel-16 draftCR to 38 101-1 for Clarification of UL Tx Switching |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R4-2306648 |
Rel-16 draftCR to 38 101-3 for Clarification of UL Tx Switching |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R4-2306649 |
Reply LS on Rel-16 UL Tx switching period |
vivo |
| R4-2306654 |
Rel-17 draftCR to 38 101-1 for Clarification of UL Tx Switching |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| 7.2.3 |
On FR2 RLM/BFD and beam sweeping from multiple directions (R5-231830) |
|
| R4-2304376 |
Response to LS on FR2 RLM BFD and beam sweeping from multiple directions |
Qualcomm Korea |
| R4-2305159 |
Discussion on LS about FR2 RLM/BFD and beam sweeping from multiple directions |
MediaTek inc. |
| R4-2305274 |
Reply LS on RLM/BFD and beam sweeping from multiple directions |
Huawei, HiSilicon |
| R4-2305800 |
Reply LS on FR2 RLM/BFD and beam sweeping from multiple directions |
Ericsson |
| 7.3 |
Moderator summary and conclusions |
|
| R4-2306180 |
Topic summary for [106-bis-e][232] Reply_LS |
Moderator (Intel) |
| R4-2306230 |
Topic summary for [106-bis-e][151] NR_reply_LS_UE_RF |
Moderator (Apple) |
| R4-2306263 |
Topic summary for [106-bis-e][232] Reply_LS |
Moderator (Intel) |
| R4-2306313 |
Topic summary for [106-bis-e][151] NR_reply_LS_UE_RF |
Moderator (Apple) |
| R4-2306388 |
Reply LS on support of per FR PRS gap |
Huawei, HiSilicon |
| R4-2306389 |
Reply LS on enhanced cell reselection in NTN |
Nokia |
| R4-2306390 |
Reply LS on FR2 RLM/BFD and beam sweeping from multiple directions |
Qualcomm |
| 8.1 |
RedCap HPUE |
|
| R4-2304404 |
On the support of RedCap HPUE |
China Telecom |
| R4-2304661 |
Discussion on RedCap HPUE |
CMCC |
| R4-2305039 |
Draft CR for enabling PC2 for Redcap UE |
China Unicom, Huawei, HiSilicon |
| R4-2305109 |
Discussions on RedCap HPUE |
vivo |
| R4-2305127 |
Views on HPUE RedCap in FR1 |
ZTE Corporation |
| R4-2305391 |
Discussion on RF impacts for RedCap HPUE |
Huawei, HiSilicon |
| R4-2305502 |
On enabling RedCap HPUE |
Qualcomm Inc. |
| R4-2305711 |
Discussion on standardization for RedCap PC2 |
MediaTek Inc. |
| R4-2305843 |
Redcap HPUE support in FR1 |
Skyworks Solutions Inc. |
| 8.2 |
RAN4 specification impact and UE implementation impact for a UE configured with two serving cells, each with SUL |
|
| R4-2304391 |
Scenarios for dual SUL |
Qualcomm Incorporated |
| R4-2304405 |
Discussion on UE configured with two serving cells and each cell with one SUL band |
China Telecom |
| R4-2304662 |
Discussion on UE configured with two SUL cells |
CMCC |
| R4-2305128 |
On UE configured with dual SUL |
ZTE Corporation |
| R4-2305568 |
Discussion on UE configured with two serving cells |
Huawei, HiSilicon |
| 8.3 |
Moderator summary and conclusions |
|
| R4-2306231 |
Topic summary for [106-bis-e][152] RAN_task_UERF |
Moderator (China Telecom) |
| R4-2306314 |
Topic summary for [106-bis-e][152] RAN_task_UERF |
Moderator (China Telecom) |
| R4-2306650 |
WF on RedCap HPUE |
China Telecom |
| R4-2306651 |
WF on RAN4 specification impact and UE implementation impact for a UE configured with two serving cells, each with SUL |
CMCC |
| 10 |
Any other business |
|
| R4-2304727 |
Further discussion on intra-band EN-DC support |
ZTE Corporation |
| R4-2304728 |
CR for TS 38.101-3 on corrections to intra-band EN-DC configurations |
ZTE Corporation |
| R4-2304729 |
CR for TS 38.101-3 on corrections to intra-band EN-DC configurations (R17_CAT_A) |
ZTE Corporation |
| R4-2304730 |
CR for TS 38.101-3 on corrections to intra-band EN-DC configurations (R18_CAT_A) |
ZTE Corporation |
| R4-2305160 |
Motivation for Rel-19 RAN4 –led WI on realistic NTN testing |
MediaTek inc. |
| 11 |
Close of the meeting |
|
| R4-2305877 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306001 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306007 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306008 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306009 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306010 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306011 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306012 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306013 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306014 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306015 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306016 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306017 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306018 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306019 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306020 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306021 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306022 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306023 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306024 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306025 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306026 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306027 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306028 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306029 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306030 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306031 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306032 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306033 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306034 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306035 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306036 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306037 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306038 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306039 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306040 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306041 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306042 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306043 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306044 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306045 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306046 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306047 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306048 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306049 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306050 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306051 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306052 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306053 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306054 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306055 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306056 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306057 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306058 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306059 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306060 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306061 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306062 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306063 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306064 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306065 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306066 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306067 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306068 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306069 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306070 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306071 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306072 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306073 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306074 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306075 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306076 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306077 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306078 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306079 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306080 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306081 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306082 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306083 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306084 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306085 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306086 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306087 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306088 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306089 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306090 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306091 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306092 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306093 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306094 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306095 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306096 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306097 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306098 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306099 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306100 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306101 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306102 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306103 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306104 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306105 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306106 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306107 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306108 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306109 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306110 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306111 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306112 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306113 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306114 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306115 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306116 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306117 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306118 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306119 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306120 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306121 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306122 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306123 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306124 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306125 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306126 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306127 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306128 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306129 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306130 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306131 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306132 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306133 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306134 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306135 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306136 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306137 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306138 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306139 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306140 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306141 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306142 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306143 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306144 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306145 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306146 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306147 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306148 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2306401 |
(reserved) |
RRM Session |
| R4-2306402 |
(reserved) |
RRM Session |
| R4-2306403 |
(reserved) |
RRM Session |
| R4-2306404 |
(reserved) |
RRM Session |
| R4-2306405 |
(reserved) |
RRM Session |
| R4-2306406 |
(reserved) |
RRM Session |
| R4-2306407 |
(reserved) |
RRM Session |
| R4-2306408 |
(reserved) |
RRM Session |
| R4-2306409 |
(reserved) |
RRM Session |
| R4-2306410 |
(reserved) |
RRM Session |
| R4-2306411 |
(reserved) |
RRM Session |
| R4-2306412 |
(reserved) |
RRM Session |
| R4-2306413 |
(reserved) |
RRM Session |
| R4-2306414 |
(reserved) |
RRM Session |
| R4-2306415 |
(reserved) |
RRM Session |
| R4-2306416 |
(reserved) |
RRM Session |
| R4-2306417 |
(reserved) |
RRM Session |
| R4-2306418 |
(reserved) |
RRM Session |
| R4-2306419 |
(reserved) |
RRM Session |
| R4-2306420 |
(reserved) |
RRM Session |
| R4-2306421 |
(reserved) |
RRM Session |
| R4-2306422 |
(reserved) |
RRM Session |
| R4-2306423 |
(reserved) |
RRM Session |
| R4-2306424 |
(reserved) |
RRM Session |
| R4-2306425 |
(reserved) |
RRM Session |
| R4-2306426 |
(reserved) |
RRM Session |
| R4-2306427 |
(reserved) |
RRM Session |
| R4-2306428 |
(reserved) |
RRM Session |
| R4-2306429 |
(reserved) |
RRM Session |
| R4-2306430 |
(reserved) |
RRM Session |
| R4-2306431 |
(reserved) |
RRM Session |
| R4-2306432 |
(reserved) |
RRM Session |
| R4-2306433 |
(reserved) |
RRM Session |
| R4-2306434 |
(reserved) |
RRM Session |
| R4-2306435 |
(reserved) |
RRM Session |
| R4-2306436 |
(reserved) |
RRM Session |
| R4-2306437 |
(reserved) |
RRM Session |
| R4-2306438 |
(reserved) |
RRM Session |
| R4-2306439 |
(reserved) |
RRM Session |
| R4-2306440 |
(reserved) |
RRM Session |
| R4-2306441 |
(reserved) |
RRM Session |
| R4-2306442 |
(reserved) |
RRM Session |
| R4-2306443 |
(reserved) |
RRM Session |
| R4-2306444 |
(reserved) |
RRM Session |
| R4-2306445 |
(reserved) |
RRM Session |
| R4-2306446 |
(reserved) |
RRM Session |
| R4-2306447 |
(reserved) |
RRM Session |
| R4-2306448 |
(reserved) |
RRM Session |
| R4-2306449 |
(reserved) |
RRM Session |
| R4-2306450 |
(reserved) |
RRM Session |
| R4-2306451 |
(reserved) |
RRM Session |
| R4-2306452 |
(reserved) |
RRM Session |
| R4-2306453 |
(reserved) |
RRM Session |
| R4-2306454 |
(reserved) |
RRM Session |
| R4-2306455 |
(reserved) |
RRM Session |
| R4-2306456 |
(reserved) |
RRM Session |
| R4-2306457 |
(reserved) |
RRM Session |
| R4-2306458 |
(reserved) |
RRM Session |
| R4-2306459 |
(reserved) |
RRM Session |
| R4-2306460 |
(reserved) |
RRM Session |
| R4-2306461 |
(reserved) |
RRM Session |
| R4-2306462 |
(reserved) |
RRM Session |
| R4-2306463 |
(reserved) |
RRM Session |
| R4-2306464 |
(reserved) |
RRM Session |
| R4-2306661 |
(reserved) |
Main Session |
| R4-2306662 |
(reserved) |
Main Session |
| R4-2306663 |
(reserved) |
Main Session |
| R4-2306664 |
(reserved) |
Main Session |